Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Advanced CI Selection and Filtering in Metric Rules

david_taggart
Mega Guru

I've a use case that requires me to setup multiple metrics rules on one server. I'll have to monitor the /home directory with one set of thresholds, but I also have to monitor the /opt directory with a separate set of thresholds.


I'm unable as of yet to create an ACC-M Metric Rule that selects only certain File Systems that are related to Linux Servers. I am able to select appropriate servers by host name with the selection criteria [Configuration Item > Name]. However I am attempting to select only one or several File Systems contained on Linux Servers. I've attempted this with numerous selection methods:

[Configuration Item > File System > Mount Point ]
[Configuration Item > Configuration item > Linux Server > Asset > Configuration Item > File System > Mount point ]
etc.

 

How do I build a metric rule that selects only specific File Systems for Metric Alerts based on specific Linux Server names? I am able to use the CMDB Query builder to achieve advanced selection criteria, how do I replicate this using Metrics Rules?

1 ACCEPTED SOLUTION

david_taggart
Mega Guru

I managed to find the answer to my own question. When creating a new Metric Rule for a Linux Server, some CI Resource Hardware metrics will give enough granularity to selectively target individual File System Mount Points.

 

While exploring available Metrics in Insights Explorer, I discovered a KPI term "disk_usage_used_percentage" would attach to individual mount points, such as root.home . When creating a Metric Rule for a Linux Server CI, searching for all metrics containing "disk_usage_used_percentage" reveals a number of different choices, each one giving a mount point in parentheses, EG: (root.home).

View solution in original post

1 REPLY 1

david_taggart
Mega Guru

I managed to find the answer to my own question. When creating a new Metric Rule for a Linux Server, some CI Resource Hardware metrics will give enough granularity to selectively target individual File System Mount Points.

 

While exploring available Metrics in Insights Explorer, I discovered a KPI term "disk_usage_used_percentage" would attach to individual mount points, such as root.home . When creating a Metric Rule for a Linux Server CI, searching for all metrics containing "disk_usage_used_percentage" reveals a number of different choices, each one giving a mount point in parentheses, EG: (root.home).