340
edits
Incidents: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 117: | Line 117: | ||
|This trigger allows to configure a list of regular expressions and is checked for each packet whose L7 data matches one of the regular expressions in the list. Since there are no attributes associated with this trigger, this effectively means that any packet which matches one of the regular expressions will result in an incident. The incident also contains information about which connection this packet belongs to as well as which of the regular expressions matches the packet. | |This trigger allows to configure a list of regular expressions and is checked for each packet whose L7 data matches one of the regular expressions in the list. Since there are no attributes associated with this trigger, this effectively means that any packet which matches one of the regular expressions will result in an incident. The incident also contains information about which connection this packet belongs to as well as which of the regular expressions matches the packet. | ||
|no attributes are available for this trigger | |no attributes are available for this trigger | ||
|- | |||
|rtp_traffic | |||
|This trigger is checked continuously for traffic of each RTP connection. The update interval is defined by the timespan parameter of the attributes. | |||
|mandatory | |||
|} | |} | ||
| Line 126: | Line 130: | ||
## ip_traffic | ## ip_traffic | ||
## qos_traffic | ## qos_traffic | ||
## rtp_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. | # 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 | ## global_traffic | ||
| Line 190: | Line 195: | ||
** throughput: The throughput bandwidth in bit/s on average during the configured timespan. | ** throughput: The throughput bandwidth in bit/s on average during the configured timespan. | ||
** packet_rate: The packet packets/s on average during the configured timespan. | ** packet_rate: The packet packets/s on average during the configured timespan. | ||
* rtp_traffic | |||
** jitter: The average jitter of the RTP connection for the given timespan, using the maximum value of both directions. | |||
** percent_loss: The percentage of RTP packet loss for the given timespan, accounting packets from both directions of the RTP connection. | |||
== Channel configuration == | == Channel configuration == | ||
| Line 233: | Line 241: | ||
Some technical limitations apply: | Some technical limitations apply: | ||
* | * continuously checked triggers like "IP traffic" are only evaluated if there was at least one packet in the corresponding time interval. Therefore, rules check for zero packet count or throughput will never match.ys | ||