Custom fields in Applications Manager allow you to add additional metadata to your monitors and monitor groups beyond the default set of fields. They provide a flexible way to categorize, tag, and organize your monitored resources based on your business requirements - such as associating monitors with specific departments, assigning labels for quick identification, or tracking impact and urgency levels for incident management.
Custom fields support multiple data types including text, lists, and predefined system fields. Values assigned to custom fields can be used across the product for filtering widgets, generating reports, configuring alarms, and more.
Applications Manager supports the following custom field types:
| Field Type | Description | Usage |
|---|---|---|
| Text | A single-line text field for entering short values. | Use for brief metadata such as application name, environment (e.g., Production, Staging), or owner name. |
| Large Text | A multi-line text field for entering longer descriptions or notes. | Use for detailed notes, descriptions, or comments about a monitor. |
| List | A dropdown list field with predefined options. You can add, edit, or remove list options. | Use when the field value must be selected from a fixed set of options, such as priority levels or project names. |
Applications Manager allows you to create and manage your own custom fields to capture metadata specific to your environment. In addition to these user-defined fields, the following predefined fields are included by default. Predefined fields are system-defined and cannot be deleted, but you can edit their values and assign them to monitors as needed.
| Predefined Field | Description | Usage |
|---|---|---|
| Label | Allows you to assign one or more labels to a monitor. Multiple values can be assigned. | Use to tag monitors with keywords for quick identification and filtering across dashboards and reports. |
| Urgency | Indicates the urgency level of a monitored resource. | Use to prioritize monitoring and incident response based on urgency. |
| Impact | Indicates the business impact of a monitored resource. | Use to classify monitors based on their business criticality. |
| Department | Associates a monitor with a specific department in your organization. | Use to organize monitors by department for reporting and accountability. |
| Configuration Item ID | A text field for associating a configuration item identifier with a monitor. | Use to link monitors with configuration management databases (CMDB) or IT asset records. |
| Description | A text field for adding a description to a monitor. | Use to provide additional context or notes about a monitored resource. |
Note:
Custom fields can be accessed from both the monitor details page and the monitor group page:
This tab displays all custom fields including the predefined fields (Label, Urgency, Impact, Department) and any user-defined fields. You can edit field values and add new custom fields from this tab.
Mark as PII: PII stands for Personally Identifiable Information. If a custom field contains PII, you can mark it as PII. Doing so encrypts the field value and stores it securely in the database. The Location field is marked as PII by default.

This tab allows you to associate users to the monitor or monitor group. The users displayed here are based on the User Management monitor group association configured for the respective users. All user roles are supported, including User, Operator, Administrator, and Manager.

This tab allows you to specify information about the physical location of the server. The available fields include Location Name, Floor, Building, City, State, Country, Postal Code, and Zip Code.

To create a new custom field:
The Add/Remove Custom Fields popup window opens.

To assign values to a custom field:
To edit an existing custom field:
To delete a custom field:
Custom field values are inherited by monitors from their parent monitor group. When you assign a custom field value to a monitor group, all monitors within that group automatically inherit the same value.
Monitor-level custom field values do not override inherited values from the parent group. Instead, both values coexist, and the monitor can be filtered using either value.
Example: If you set the Department field to "IT Operations" for a monitor group named "Production Servers", all monitors within that group will inherit "IT Operations" as their Department value. If you then set a monitor-level value of "Other Operations" for a specific monitor, both "IT Operations" (inherited) and "Other Operations" (monitor-level) will be associated with that monitor. The monitor can be filtered using either value.
Custom fields can be used in various areas of Applications Manager for filtering, reporting, and automation:
Note:
Custom fields are available as filter criteria in dashboard widgets. You can filter widget data by custom field values to display monitors that match specific criteria, such as a particular label, department, or impact level.
When performing bulk configuration actions, you can use custom fields to filter and select the target monitors. This allows you to apply configuration changes to monitors that share specific custom field values.
In the Alarms tab, you can filter alarms based on custom field values. This helps you quickly identify alarms associated with specific departments, labels, or priority levels.
Custom fields are available as filter criteria when generating reports. You can generate reports for monitors that match specific custom field values to focus on relevant subsets of your monitored infrastructure.
Custom field values are indexed and searchable through the product search functionality. You can search for monitors by their custom field values using the global search bar, allowing you to quickly locate monitors associated with specific labels, departments, or other custom metadata.
Custom field values can be used as replaceable tags in notification templates and actions. This allows you to include monitor-specific custom field data in alarm notifications, emails, and other automated actions.
The custom fields feature is available in both Professional and Enterprise editions of Applications Manager. However, there are differences in how custom fields are managed in the Enterprise edition:
Note:
It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.
Reviewer Role: Research and Development