Automatic monitor state changing
Assignee
Pavel Salamon
Pavel SalamonReporter
Pavel Salamon
Pavel SalamonLabels
Sprint
None
Description
Steps to reproduce
None
relates to
Activity
Show:
Martin Zatopek September 29, 2020 at 10:57 AM
Code reviewed, related issue detected in cluster, see https://cloverdx.atlassian.net/browse/CLO-19732#icft=CLO-19732.
Pavel Salamon September 3, 2020 at 3:28 PM
Monitors react to events and change their state automatically.
Automated tests will be done separately https://cloverdx.atlassian.net/browse/CLO-19643#icft=CLO-19643.
Needs code review.
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