up.time uses Uptime Infrastructure Monitor uses two types of regular expression syntax:
| Table of Contents |
|---|
Wildcard
The wildcard regular expression syntax only supports an asterisk (*) at the end of an expression. You can use wildcards with the following reports and monitors:
...
| Note | ||
|---|---|---|
| ||
Note that a wildcard will include all disks or file systems that match an expression. For example, if you specify |
Java Regular Expressions
up.time Uptime Infrastructure Monitor also supports the full range of Java regular expressions, as well as inverse regular expressions. For example, you can specify /u.* to include or exclude all file systems with names that begin with u. The inverse regular expression [^OK], on the other hand, will return all results that are not in an OK state.
| Note | ||
|---|---|---|
| ||
| The matching performed by Java regular expressions in up.time Uptime Infrastructure Monitor is case sensitive. |
The following monitors support Java regular expressions:
- Windows Event Log Scanner
- DNS
- FTP
- HTTP
- IMAP
- Custom
- NIS/YP
- NNTP
- POP
- SMTP
- TCP
- SNMP
Sample Regular Expressions
The following examples of Java regular expressions can be used with the Windows Event Log Scanner and POP monitors.
...
[OK POP3 .* server ready]
Literal Characters
The following characters have special meaning in a regular expression and must be escaped using a backslash (to indicate that the characters should be interpreted literally):
...