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

Automatic monitor state changing

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: rel-5-8-0
    • Component/s: None
    • Security Level: Users (General product issues)
    • QA Testing:
      UNDECIDED
    • Sprint:
      Blue Sprint 106, Blue Sprint 107, Blue Sprint 108

      Description

      Monitor should change its internal state automatically.

      Automatically react to state changes of its elements (schedules, listeners, data services) or the elements in monitored sandboxes.

       

      Example:

      When monitor is in OK state and then some monitored scheduler gets into FAIL state, the monitor should automatically move to FAIL as well.

      When monitor is in FAIL state and then some listener gets into OK state, the monitor should automatically switch as well (as long as there are no other failing monitored elements).

       

      All the possible causes of state change should be covered by automated API test - framework for tests will be implemented in CLO-19534

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              salamonp Pavel Salamon
              Reporter:
              salamonp Pavel Salamon
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: