Incidents: Difference between revisions
Jump to navigation
Jump to search
Access restrictions were established for this page. If you see this message, you have no access to this page.
(Created page with "<nowiki><accesscontrol></accesscontrol></nowiki> Incidents are just to alarm the user when configured events appear, usually for traffic based rules, but also for system-spec...") |
No edit summary |
||
| Line 6: | Line 6: | ||
Occurred incidents can be seen in the web interface, and additionally reporting via email or syslog is possible too. | Occurred incidents can be seen in the web interface, and additionally reporting via email or syslog is possible too. | ||
=== Rule configuration === | |||
TODO | |||
=== Channel configuration === | |||
TODO | |||
=== Other incidents settings === | |||
TODO | |||
=== Occured incident view === | |||
TODO | |||
=== Rule statistics === | |||
TODO | |||
Revision as of 15:38, 3 February 2021
<accesscontrol></accesscontrol>
Incidents are just to alarm the user when configured events appear, usually for traffic based rules, but also for system-specific events.
The incident feature allows to define rules which are checked on the configured trigger point, like when a connection ends, a SIP call ends, or for checks on ongoing traffic. When such a trigger hits, configurable traffic attributes will be checked and if all attributes of a rule matches, an incident is created.
Occurred incidents can be seen in the web interface, and additionally reporting via email or syslog is possible too.
Rule configuration
TODO
Channel configuration
TODO
Other incidents settings
TODO
Occured incident view
TODO
Rule statistics
TODO