122
edits
Incidents: Difference between revisions
→Available triggers
mNo edit summary |
|||
| Line 113: | Line 113: | ||
|This trigger is checked continuously for the total traffic of the device. The update interval is defined by the timespan parameter of the attributes. | |This trigger is checked continuously for the total traffic of the device. The update interval is defined by the timespan parameter of the attributes. | ||
|mandatory | |mandatory | ||
|- | |||
|global_regex_match | |||
|This trigger allows to configure a list of regular expressions and is checked for every packet that matches one of the regular expressions on the list. As there are no attributes associated with this trigger this effectively means that any packet that matches one of the regular expressions will result in an incident. The incident will also contain information to which connection this packet belongs as well as which of the regular expressions was matched by the packet. | |||
|no attributes are available for this trigger | |||
|} | |} | ||