All incidents in InfiMONITOR NEXT are generated according to the rules that describe the conditions under which the incidents should be created.
The incident's severity helps network engineers to correctly prioritize the problems identified by the monitoring system in the wireless network. The higher the priority, the more important is the problem. InfiMONITOR NEXT provides 3 levels of severity:
The priority is defined in the incident generation rule.
An incident's life cycle includes several stages described in the table below.
Stage | Incident status | Description |
---|---|---|
Fulfillment of the rule condition | The incident condition specified in the rule is met, confirmation procedure is started. Incident is not created at this stage. | |
Confirmation of the incident | Fulfillment of the rule condition will be checked during the confirmation time. If condition is met for the entire time, an incident will be created. If the condition is not met at least once, an incident is marked as not confirmed and its lifecycle ends. | |
Incident creation | Open | Created incident may be assigned to a responsible person. In this case incident will be moved to the "Incident processing" stage. Otherwise the rule condition fulfillment will be checking periodically during the regular polling cycle. If the condition is not met at least once the incident will be moved to the "Confirmation of the incident resolving" stage. |
Incident processing | In service | Responsible person performs actions to eliminate the incident reason. The rule condition fulfillment is checking periodically during the regular polling cycle. If the condition is not met at least once the incident will be moved to "Confirmation of the incident resolving" stage. |
Confirmation of resolving | Open / In service | Fulfillment of the rule condition will be checked during the confirmation time. If condition is not met for the entire time, incident will be moved to the "Closure" stage. Otherwise incident will be moved back to the previous stage: "Incident creation" or "Incident processing" depending on whether a responsible person is assigned or not. |
Closure | Resolved | This stage is final, the incident is resolved. |
"Resolved" status is final and means that the incident was closed. If the incident conditions are met again, a new incident will be created.
The incident will be available to the monitoring system user only if the device is in the user's visibility area.
Each rule has the following structure:
Each rule contains the list of device groups for which it will be applied. There are the following categories may be used to define the rule scope:
Each condition is described by the following parameters:
Confirmation time - time period during which confirmation of an incident is performed. At this period the polling frequency of the corresponding device is increased to one per minute.
Incident rules are managed in the "Incidents" section - "Incident rules":
By default, there are two rules are added to InfiMONITOR NEXT:
To create a new rule, click on the "Add new rule" button. Fill the form:
The next step is to specify the conditions for the incident creation. The reference value set by the rule's conditions will be compared with the actual value obtained during the polling process of the wireless device.
For example, it is necessary to generate incidents when CPU load exceeds 75% during 5 minutes and memory usage is not less than 50%. For this, in the incident condition, we should set the following values:
To complete the rule configuration, click on the "Save" button. The rule will be used starting with the next polling cycle of the wireless device.