...

An InfiMONITOR NEXT user can obtain a list of all the incidents for the wireless devices and the links in his visibility area by going at the "Incidents" section.

The section includes two key areas:

• Incidents list - all incidents for the devices and the links in the user's visibility area are displayed here.
• Incident card profile side view  - if this area is open, an incident card profile with detailed information will be displayed without hiding the list of incidents.  If If the area is hidden, then the selected incident card profile will be opened, but the list of incidents will be hidden.

For easy operation with the incidents list a filter is available at the top of the page. Besides the standard filter by incident occurrence period, additional filters allows to sort incidents by the following parameters:

• assignee;
• status;
• severity;
• rule;
• object.

Incidents review

The incidents list is presented in a table having the following columns:

• Created - the date and time when incident was created.
• Incident - it displays the title and severity of the rule according to which the incident was created.
• Object - the device for which the incident was created.
• Status - current incident's status. The possible statuses are described in the Incident management article.
• Device - the device for which the incident was generated.
• Date - the date at which the incident was generatedAssignee - user who was assigned for resolving this incident.
• Updated - the date and time when the rule conditions were met last time.

By default, all incidents are sorted by date, therefore the new incidents will be displayed first.

Incident

...

profile

A card profile contains the following detailed information:

• "Description" - the device or link for which the incident was generated will be displayed here. Also there is a description from the appropriate rule.
• "Status" - current incident status.
• "Assignee" - user responsible for handling the incident.
• "Source" - rule title.
• "Scheme":
  • Device incident - additional information about the device, including its status, model and IP address.
  • Link incident - additional information about the devices connected to the link for which the incident is generated.
  • There is possibility to switch to the web interface of each device or to manage it via the command line.
• "Comments" - comments added by engineers to this incident.

Incident processing

...

To accept an incident, the user must click on the "Take on" button in the incident 's cardprofile. This will lead to the following changes:

• The incident's status will change to "In service".
• The incident will be assigned to the user, which will be reflected in the "Assignee" field.

If the incident's rule contains the conditions for its automatic closure, then the incident Incident will be resolved automatically closed after eliminating the cause. If the engineer eliminated the incident cause, but the rule does not have the conditions for the automatic closure, then the user can manually change the status of the incident to "Resolved". If the user does not manually change the status, then the incident will become obsolete with the status "Aged".The engineers In this case the rule conditions won't be met and incident will be closed with status "Resolved".

Engineers can leave comments in the incident card profile that will be visible to other engineers, whose visibility area includes the particular device.

...

The monitoring system users can receive notifications about incidents. To activate notifications, configure the connection to the email server (see System configuration).

InfiMONITOR NEXT sends notifications containing incidents related to the devices and wireless links in the user's visibility area. Notifications are sent every 30 seconds and include all changes, accumulated during this time period.

...

Here the user can select the incident severity levels for the notifications he wants to receive.

The "Group" option activates joining of several incidents with the same severity level into one notification. In this case each notification will include incidents with the same severity only.