104
edits
Incidents: Difference between revisions
Update names of web page tab headlines
(Add new wifi handshake trigger and attributes) |
(Update names of web page tab headlines) |
||
| Line 17: | Line 17: | ||
== Rule configuration == | == Rule configuration == | ||
[[File:Incidents rules.png|thumb|600x600px|Rule configuration]] | [[File:Incidents rules.png|thumb|600x600px|Rule configuration]] | ||
Incident rules can be defined in the | Incident rules can be defined in the Incident rules" tab in the menu "Generic -> Incidents". All changes to the rule configuration will only take effect after saving the current configuration by clicking on the save button at the bottom of the page. | ||
The page shows a table containing the existing rules and their configuration. | The page shows a table containing the existing rules and their configuration. | ||
| Line 42: | Line 42: | ||
* IP group: Depending on the selected trigger, the rule can be applied to an IP group instead of an individual IP address. | * IP group: Depending on the selected trigger, the rule can be applied to an IP group instead of an individual IP address. | ||
* Virtual link group, IP and IP filter can also be used inversely by using the != comparator | * Virtual link group, IP and IP filter can also be used inversely by using the != comparator | ||
* Report channel: Incidents are always visible in the web interface, but can also be reported via multiple channels which can be configured separately in the tab " | * Report channel: Incidents are always visible in the web interface, but can also be reported via multiple channels which can be configured separately in the tab "Notification channels". Up to ten channels can be selected so that the incident for this rule is reported on each channel. Also, no channel can be configured so the incident is only accessible on the web interface. | ||
* Aggregation of recurring Incidents: Incidents are aggregated by default. This means the table only shows the number of incidents of the type and the timestamps of the first and the last incident. This can be disabled for most of the incidents, so that you are able to see every indent of the incident-type. | * Aggregation of recurring Incidents: Incidents are aggregated by default. This means the table only shows the number of incidents of the type and the timestamps of the first and the last incident. This can be disabled for most of the incidents, so that you are able to see every indent of the incident-type. | ||
* Time Profiles: You are able to set a profile which defines the active time of an incident rule. | * Time Profiles: You are able to set a profile which defines the active time of an incident rule. | ||
| Line 487: | Line 487: | ||
The number of incidents available in this view is limited by a configurable number (firmware <4.1 was limited to 1000), the configuration as available in the "Other settings" tab. | The number of incidents available in this view is limited by a configurable number (firmware <4.1 was limited to 1000), the configuration as available in the "Other settings" tab. | ||
== | == Incident statistics == | ||
[[File:Incidents stats.png|thumb|600x600px|Statistics about rules]] | [[File:Incidents stats.png|thumb|600x600px|Statistics about rules]] | ||
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. | 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. | ||