CMDB Health dashboard issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I am configuring the health dashboard. The staleness metric is creating an issue of "Max Failures". When I checked the Stale CIs on health dashboard, all are retire and updated on 10 months ago. Due to this issue Correctness metric is not Visible on graph. Kindly have a look and provide me the solution.
Thanks
Mirza
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
ahoy @MirzaSaquiB,
if I remember correctly the threshold for being stale is 60 days, check this value.
Validation:
- check the total number of CIs and mark it,
- update any of these 10 months ago,
- then check the metrics again and compare to the amount from the first step
✂-----Cutting-out-the---✦AI-noise✦---All-replies-written-and-vouched-for-by-GlideFather---
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @MirzaSaquiB ,
Can you apply a Health Inclusion rule to exclude retired CIs (if none exist) where - Install state is not Retired, Metric - Staleness and re run the correctness job for the affected CI class.
For example:
By Default - Staleness failure threshold is 50K records - just FYI
Hope this helps!
Thank you,
Hemanth
Certified Technical Architect (CTA), ServiceNow MVP 2024, 2025,2026
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @MirzaSaquiB ,
You will need to put in a filter condition in your Health inclusion rule. Navigate to Class Manager-> Pick up the class where the rules are setup if you have a single rule. If you have multiple health rules for different classes for staleness, you will need to modify each of them. The modification will include addition of a filter condition : Install Status = Installed or Install Status != Retired or Install Status is one of -(any state as per business requirement).
Regards,
AJ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I hope it does not matter what is the discovery source. Correct?
In my case all the retire Cis belong to VMware Virtual Machine Instance. and discovery source is cloud Discovery.
