Page tree

SAYMON документация

Skip to end of metadata
Go to start of metadata

Both alarm generation conditions and State change conditions can generate incidents.

In spite of these features are similar, they have essential differences.

With generating alarms, manually created levels are available as well as the four default levels:

ALARM
CLEARED
MAJOR
WARNING

Incident functionality is optional and disabled by default. To enable it the following parameters must be added or modified:

Conditions priority

By default (if Alarm generation conditions are not defined) incidents are generated for objects in the states ALARM, OVERLOADED or NO DATA, which are defined in State change conditions.

The presence of Alarm generation conditions disables incident generation by State change conditions, but does not disable defined states changing rules.

One or several incidents

An object can be in one state at a time, so:

  • State change conditions create only one incident for one object at a time;
  • Alarm generation conditions allow to create several incidents for one object.

For example, there is an object to check temperature (T) and humidity (H).

The following State change conditions are set:

  • if T > 30, then change the state to the ALARM one;
  • if H > 50, then change the state to the OVERLOAD one;
  • else change the state to the WORKING one.

The data T = 31, H = 51 come from the object.

In this case:

  • the object will be transferred to the ALARM state;
  • an incident  ALARM will be generated about the ALARM state.


Then the following Alarm generation conditions are added:

  • if T > 30, then generate an incident ALARM;
  • if H > 50, then generate an incident WARNING.

The data T = 31, H = 51 come from the object once again.

In this case:

  • the object will be transferred to the ALARM state;
  • two incidents: ALARM and WARNING will be created.

Incidents autoclearing and clear conditions

If Alarm generation conditions are not defined, an incident will be cleared if the object changes its state to any one, except for the states ALARM, OVERLOADED or NO DATA.

In the case of presence of Alarm generation conditions, the incident will be cleared if:

  • the condition to generate this incident is not valid anymore

or

  • this incident has got its own clear condition added with the button , and this condition is met.

Actions on state changes

The functionality Actions on state changes depends on State change conditions only.

Presence or absence of Alarm generation conditions does not affect on  State change conditions and actions on state changes.

Synthetic alarms

Synthetic alarm is an alarm, generated by one or several regular alarms embedded in it.

If several synthetic alarms are specified for one object, then the lower it is in the list of alarms, the higher priority it has.

There are the rules regarding the mechanism of synthetic alarms generation:

  • an individual alarm is generated for each object;

  • after receiving the clearing message, the alarm is colored green with the status CLEAR and:
    • if a similar alarm occurs before N (configurable trashhold time) minutes, then the alarm resumes;
    • if a similar alarm occurs after N minutes, then a new alarm is created;

  • the transition from the list of active alarms to the list of historical alarms occurs in M minutes after receiving a clearing message (is configurable time during which the alarm remains in the list of active alarms after its completing);

  • the time of displaying a completed alarm in the active list should be greater than or equal to the trashhold time: M is greater than or equal to N;

  • a synthetic alarm closes after closing of all nested alarms.


If it is necessary to generate the same synthetic alarm for several objects, the window Search and bulk operations can be useful:

Synthetic alarm can be formed on the basic of two or more synthetic alarms, generating the double level of nesting.

  • No labels