Every item that is monitored in Sentinel is in a certain state, at any point whilst the monitor is running.<\/p>\n
As a new input is evaluated, its state can change.<\/p>\n
For each input in a test, the initial state depends on the process used. After the test is triggered, new sample data is collected at every sample interval. The sample data is evaluated against predefined limits. If a sample value exceeds a limit, then a new state is reached.<\/p>\n
State duration lasts until a new state is reached.
\nState duration is measured to the nearest second.<\/p>\n
The start time of an event for an entity is the time that the current state was reached. When the state changes, there is a new start time for the event.<\/p>\n
The state severity is specified in the state configuration of a test. There are five severities that can be used to classify the different states:<\/p>\n
The default severity for all of the states is None<\/strong>.<\/p>\n When a test runs, any input values are evaluated for the periods when the precondition is true. For the periods that the precondition fails, the test monitor item goes into a suppressed<\/strong> state.<\/p>\n If there is low confidence data for an entity that is being tested, then the resulting state for that entity will be suppressed<\/strong>.<\/p>\n A third circumstance which may cause a suppressed state is Test Suppression, whereby testing is deliberately suppressed for a specific reason.<\/p>\n The following states can be reached, depending on which process is being used by the test:<\/p>\n For more information about which states apply to the various processes, refer to each process<\/a>.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Every item that is monitored in Sentinel is in a certain state, at any point whilst the monitor is running. As a new input is evaluated, its state can change.<\/p>\nSuppressed State<\/h2>\n
\n