CMDB Health dashboard issue

[MirzaSaquiB]

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

[AJ_01]

It depends on your business use case. If you want to target and remove only a specific Discovery Source of Retired devices from your Staleness count, you can manage that in the inclusion rule. Else you can ignore all retired CIs irrespective of the discovery source by not mentioning the discovery source in the filter condition.

Attached screenshot, use the filter condition for any configuration that suffice your requirements. 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards

 

[MitulTailor]

Mirza, the retired CIs hitting your staleness threshold are telling you something the exclusion rule will hide.

Those VMware instances were retired but never had a decommission record raised. So the CMDB marked them retired by state, not by process. Run a quick report: Retired CIs in that class with no associated CHG or REQ in the last 12 months. That count is your real problem. The dashboard fix is one line in the inclusion rule — Hemanth's answer is correct. But if you do not run that report first you will have the same conversation again in six months with a different class.

Built a scoring tool that flags exactly this kind of Correctness gap before it shows up in the dashboard. mitultaylor.github.io/it-tools