Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-19622

Operations Dashboard log

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: rel-5-8-0
    • Component/s: Server
    • Security Level: Users (General product issues)

      Description

      Oprations Dashboard shows current status of all Monitors but it isn't possible to investigate history of the Monitors. With automated 'healing' the Monitor might change state from green to red, then back from red to green while support staff is not watching screens (weekend, night). Once they are back at screens, investigating a past incidents seeing events of Monitor state change (timestamp of event, triggers causing state change) will make their work easier.

      Introduce separate log file suitable for auditing history of the Monitors. The log should contain info about change of monitor's health status (ok -> fail, fail -> ok). List of failing triggers should be logged in case of ok -> fail state transition.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              salamonp Pavel Salamon
              Reporter:
              slamam Martin Slama
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: