- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-13-2017 07:58 PM
Hello
I am not sure why staleness on CMDB Dashboard is showing 100%. I have discovery running on daily basis.
Please advise, where do I need to make changes?
Thanks,
Rajan Mehta
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-14-2017 09:59 AM
Hi,
It represents the amount of CIs that are affected by the metric.
If the calculation goes past the failure threshold value, the job is terminated and you will see a numeric value of CIs affected in meter e.g. " Staleness 50589/50589". If you hoover the cursor over the info-sign in front of the metric name, it will give you additional information.
Set the failure threshold to a higher level and re-run the scheduled job.
When the job finishes succesfully, you will see a green dot in metric name and the metcic will show the sum of "affected CIs/total amount of CIs".
- Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-28-2021 11:43 PM
Hi,
I have a requirement to implement the health dashboard. I activated the OOB in that it is not calculating the staleness metric in correctness scorecard showing " Failure threshold reached". I even tried setting the failure threshold value to more higher. In our cmdb we have more that 23 lakhs of CI and among which 19 lakh of CIs are stale. So i set the failure threshold value to 2200000. but it took more time to complete the schedule job running even though it fails. Please advice me.