Discovery Filters

• Overview
• Syntax
• Supported monitor types
• Examples

Overview

Applications Manager allows you to discover resources in a monitor type based on various filtering conditions. You can choose to filter resources for discovery based on the regex filters for the particular monitor. It discovers resources that matches the specified regex filter from the server and monitors their performance and availability.

Note: This option is only available in the Docker, VMware ESXi, RabbitMQ, IBM WebSphere MQ and Microsoft Azure monitors.

Syntax

<ModuleType>_<AttributeName>=[Regex]

where,
<ModuleType> - Module type to be monitored.
<AttributeName> - Name of the attribute to be monitored.
[Regex] - Regex value to be specified.

Following are the list of points that are to be noted for entering a valid regex filter:

• Users can provide multiple filters separated by comma and provide appropriate conditions/symbols such as "||" (OR), "&&" (AND) and "[]" between the filters with different attribute names to create multiple options.
• Users should not use the characters _ [ ] in the regex value as they are used as a separator and for grouping functionality.
• Users can provide discovery filter regex for multiple Module Types of the same monitor type. However, they cannot group multiple Module Types in the Discovery Filter regex. Example: CONTAINER_NAME=tomcat.* && NODE_NAME=test.*
• In case the user provides any invalid module type or an attribute name that is not supported, an error message will be shown during the monitor addition.
• Attribute names, module names and regex are case-sensitive.

Supported monitor types

Following are the list of monitor types that support discovery filters:

Examples

Following are some examples by which regex filters can be specified: