115
edits
Incidents: Difference between revisions
→2. Channel configuration
No edit summary |
|||
| Line 146: | Line 146: | ||
=== 2. Channel configuration === | === 2. Channel configuration === | ||
Incidents can be reported on different channels. The configuration allows to add new channels so they can be selected in the rule configuration described above. | |||
Each channel can be of type: | |||
* email: Incidents will be sent to the email address configured in the [[Global settings]]. | |||
* syslog: Incidents will be sent to the configured syslog server via TCP on port 514. | |||
Each channel also uses a minimum severity settings so only incidents are reported which are of at least that severity. | |||
Some incidents cannot be configured via rules and you can choose to get those incidents also via email by enabling the settings at the lower part of the settings page. | |||
=== 3. Other incidents settings === | === 3. Other incidents settings === | ||
Incidents that cannot be configured separately via rules can be configured on this page. | |||
=== 4. Occured incident view === | === 4. Occured incident view === | ||
This page shows up to the last 1000 incidents occurred on the system. The table can be filtered for specific severity levels, as well as for specific trigger sources by selecting the trigger from the drop down menu. | |||
The list can also be filtered for the subject of the incident. | |||
Individual incidents can be view in detail by clicking on the subject. The details page shows detailed information including links to the relevant measurement page. | |||
Incidents can be deleted individually by clicking on the delete button next to the incident, or all incident can be deleted by clicking on the button on the top right of the page. | |||
=== 5. Rule statistics === | === 5. Rule statistics === | ||
This page shows graphs about how often each rule has been hit both in absolute numbers as well as relatively to how often the rule has been checked. | |||