CMDB Health Dashboard
Measuring completeness, correctness, and compliance.
5 questions loaded · 4 definitive · 1 scenario
Definitive questions
Scenario drills
Completeness score suddenly drops 20 points
“Overnight the Windows Server completeness KPI drops from 88% to 68%. What do you check?”
Approach
- New required attribute was added (or made mandatory) on the class — every existing CI now fails.
- Discovery pattern change stopped populating a field.
- MID Server outage caused stale last_discovered timestamps, hiding data.
new GlideRecord('cmdb_health_result') .addQuery('ci_class','cmdb_ci_win_server') .orderByDesc('sys_created_on');Alternate approach
Alternate: diff the sys_dictionary_history for that class over the last 24 hours — usually shows the config change that moved the score.
Pitfall
Chasing 'bad data' when the root cause is a governance change that added a new required field.
Grow this section
Generate more unique questions on demand — the AI sees the titles already on the page and avoids repeats. Repeat until you reach the depth you need.