article Regular Expression Syntax Used with up.time

Related Documentation Version of up.time affected Affected Platforms
All All

up.time uses two types of regular expression syntax:


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:

  • File System Capacity Growth report
  • Disk I/O Bandwidth report
  • File System Service Time Summary report
  • File System Capacity monitor
  • Platform Performance Gatherer

When used with the reports and monitors listed above, a wildcard includes or excludes disks and file systems. For example, if you want to configure the File System Capacity monitor to exclude the /lib and /lost+found file systems on a Solaris server, you can specify the regular expression /l* in one of the Exclude Pattern fields on the monitor template.

Note that a wildcard will include all disks or file systems that match an expression. For example, if you specify /us* in the Exclude File Systems field when creating a File System Service Time Summary report then this expression will force the report to ignore the /users, /usr, and /usr/local file systems.

Java Regular Expressions

up.time 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 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.

The Windows Event Log Scanner searches a specified number of lines in a Windows log file for a specified text string. For example, you want to search the System log to find disks that are full. Since certain Windows systems have more than one disk drive, you can use this regular expression to ignore specific drive letters:

Disk .: is full

The POP (Email Retrieval) monitor checks the status of POP2 and POP3 servers. You can enter a regular expression in the Expected Server Response field of the monitor template to determine if a connection is made to the POP service. For example, entering the following regular expression will direct the POP monitor to look for all server responses that contain OK POP3 and server ready messages:

[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):

] (
) {
} ^
. ?
* +
| $

For example, to find the the string (some_text), use the regular expression (some_text).

Related Articles

'Default up.time data store' monitor crit after adding a vCenter ...


As part of the initial install of up.time, the Monitoring Station itself is setup as an element within up.time. This sample element is initially setup to use localhost as it's hostname, along...

By: uptime Support | Date Created: 3-8-2013 | Last Modified: 3-8-2013 | Index: 592


Integrating up.time NetFlow with up.time


Learn how to configure up.time to point to your Scrutinizer instance to enable click-through graphing, as well as an integrated Scrutinizer view from Global Scan.

By: uptime Support | Date Created: 7-8-2010 | Last Modified: 2-8-2013 | Index: 459


Monitoring WebSphere with up.time


Use up.time to monitor the performance and health of Java applications running on WebSphere servers.

By: uptime Support | Date Created: 12-20-2006 | Last Modified: 7-26-2011 | Index: 108


The up.time Data Collector is unavailable


By: uptime Support | Date Created: 6-9-2006 | Last Modified: 10-17-2013 | Index: 077


Resolving JVM_BIND Errors in up.time


By: uptime Support | Date Created: 6-7-2006 | Last Modified: 8-9-2011 | Index: 075


User Comments

No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement