<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Regular Expressions

For some sensors (for example, some HTTP sensors and email sensors), you can use regular expressions to match a search pattern. PRTG supports Perl Compatible Regular Expressions (PCRE).

PRTG does not support regex options or regex flags like, for example, /g (global), or /s (single line), or /gs, and will not correctly search for the target string if you try to set options.

See below for examples with the most common patterns and an example for possible matches.

Common Search Patterns

Find matches containing the word error or alarm:

\b(error|alarm)\b

 

Find matches containing the words error and alarm, in any order:

(?=.*\berror\b)(?=.*\balarm\b).*

 

Find matches containing all of the words tree, flower, leaf, and bug, in any order:

(?=.*\btree\b)(?=.*\bflower\b)(?=.*\bleaf\b)(?=.*\bbug\b).*

 
It is not possible to match an empty string using the PRTG regex search with sensors.

Example

The search pattern

(?=.*\berror\b)(?=.*\balarm\b).*

will match the following expressions:

• alarm error
• error alarm
• I am an error and I evoke an alarm
• I am an alarm and I indicate an error
• An alarm combined with an error indeed!
• An error combined with an alarm, too!

More

Regex101: Test and debug your regular expressions

• https://regex101.com/

Regex Tester: Test Regular expressions interactively

• http://regexpal.com

Wikipedia: Regular expression

• http://en.wikipedia.org/wiki/Regular_expression

 

Advanced Topics

• Active Directory Integration
• Application Programming Interface (API) Definition
• Filter Rules for xFlow, IPFIX, and Packet Sniffer Sensors
• Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
• Define IP Ranges
• Define Lookups
• Regular Expressions
• Add Remote Probe
• Failover Cluster Configuration
• Data Storage
• Using Your Own SSL Certificate
• Calculating Percentiles