Creating Custom Monitor Conditions
Monitor Conditions let you control the severity reported by nodes in the Monitor Nodes screen. You can create your own custom Monitor Conditions.
For each Monitor Node that contains leaf Monitor Nodes (in other words, Monitor Nodes without children), you can create Monitor Conditions that evaluate REL expressions that return a severity value. The highest severity that applies is displayed in the Monitor Nodes screen.
You can also use Monitor Conditions to suppress severities (for example, on a Job Server that is intentionally shutdown for a long time).
Job Server and Queue performance monitors can also be configured this way. Note that Performance monitors are disabled by default. You can add Monitor Conditions to set the severity.
You can create Monitor Conditions for each value. For information on values available for Job Servers, see Monitoring External Systems with Platform Agents.
Example
For example, on a Job Server, you can set the following Monitor Conditions to monitor CPU usage.
Field | Value |
---|---|
Name | CPUsageGood
|
Description | Normal CPU usage
|
Expression | =CPUBusy > 50
|
Severity | 25
|
Field | Value |
---|---|
Name | CPUsageHigh
|
Description | High CPU usage
|
Expression | =CPUBusy > 90
|
Severity | 50
|
Field | Value |
---|---|
Name | CPUsageCritical
|
Description | Critical CPU usage
|
Expression | =CPUBusy > 95
|
Severity | 75
|