547
edits
Incidents: Difference between revisions
→1.2. Available triggers
No edit summary |
|||
| Line 114: | Line 114: | ||
|mandatory | |mandatory | ||
|} | |} | ||
===== 1.2.1. Special trigger properties ===== | |||
Some trigger are checked continuously every configured time span period, so the incidents are generated differently than for fixed event specific triggers like a call end. | |||
# Repeating incidents: The following triggers will be evaluated every configured time span and will be re-issued whenever the configured attributes match. | |||
## mac_traffic | |||
## ip_traffic | |||
## qos_traffic | |||
# Start/stop incidents: The following triggers are reported once the configured attributes match and for a second time when the attributes no longer match. | |||
## global_traffic | |||
This means you will get repeated incidents for the same element every time span. For example, if an IP address has traffic of 100 mbit/s for 2 minutes and a rule checks for more than 50 mbit/s over 30 seconds, the rule will hit 4 times. There will be one incident which will contain the exact number of repetitions for reference. | |||
For start/stop incident, you will only see two rule hits and the incident description will state the start and stop time. | |||
==== 1.3. Available attributes ==== | ==== 1.3. Available attributes ==== | ||