CMDB Health Dashboard, under compliance shows " No Data Job Completed, however there were no CIs"

[suuriyas]

HI Community,

In CMDB Health Dashboard, under compliance it is showing as like this "

No data available

Job Completed, however there were no CIs available to evaluate"

what does it means? where i need to check this and for other 2 completeness and correctness data is getting displayed but for this alone it is showing as no CI's .

On what basis it is showing as no data where/how  can i check that

Thanks in Advance 

[Michael de Boer]

Hi @suuriyas 

It's strange that the audit "Model ID of a workstation should not be 'Unknown' or 'Default String'" has a template related to it, but the version isn't mentioned in the name.
As you can in the other audit rule the template name ends on " - 4" to show template version 4 is used.
Can you compare this on the other instances?
Or open the audit rule "Model ID of a workstation should not be 'Unknown' or 'Default String'" and select the latest active template.

[SIVASANKARIS]

Hi @suuriyas ,

The message “No data available – Job completed, however there were no CIs available to evaluate”
simply means that no compliance rules are currently configured, so the system has nothing to evaluate.

---

What is Compliance in CMDB Health?

Compliance checks whether your CIs follow predefined standards or policies.

Simple example: 

Let’s say you define a rule:

All Windows Servers must have the “Operating System” field populated.

• If OS field is filled → Compliant

• If OS field is empty → Non-compliant

This rule is what we call a compliance rule.

---

How Compliance works in Backend

Compliance is driven by these tables:

Table Purpose

cert_template	Defines what rule to check
cert_filter	Defines which CIs to check
cert_audit	Stores the evaluation results

---

Why it works in TEST but not PROD

Since you mentioned:

TEST shows compliance data
PROD shows "No CIs"

Most likely:

✔ TEST has compliance rules configured
❌ PROD does not have rules configured

Please navigate in PROD and verify:

• cert_template – Are there any rules present in this table?

• cert_filter – Is CI scope defined in this table?

• cert_audit – Are any audit records generated. If these tables are empty in PROD, it confirms no compliance rules exist, which is why the dashboard shows No Data.

---

Where to define Compliance Rules

You can configure rules from:

CI Class Manager → Select CI Class → Health → Compliance

Here you define:

• Which field to validate

• Expected value / condition

• Which CI class it applies to

If this section is not visible, please ensure:

• Correct roles (admin / cmdb_admin)

• Plugins are enabled

If you find these helpful.. Please Mark it as helpful and accept my solution... 

[suuriyas]

HI @SIVASANKARIS ,

Thanks for the brief explanation

I understand this but the thing is under compliance we have the rule set up.

Data is mentioned in all 3 and they are active records. (certification template, filter and audit) but still under the audit record i don't see any CIs i also manually ran the audit to check but still i don't see any records there.

Under certification filter, the record has this condition as you can see there are records which satisfy this condition but in audit it is not showing any records i don't know why

recently cloned dev to prod same case happened in dev as well no data shown but when i ran the audit i can see records under audit result and then i ran the scheduled jobs then i was able to see the data in dashboard. did the same in prod but no results.

[suuriyas]

@SIVASANKARIS @Michael de Boer 

One thing i noticed in prod is these dates are in past last and next run date.....even tho i ran the audit it is not updating

[SIVASANKARIS · Accepted solution]

Hi @suuriyas,

Since you’ve confirmed that the configurations (Template, Filter, and Audit) exist but manual runs aren't generating Audit Results, the issue isn't a lack of rules—it’s an execution failure.

Based on the fact that your "Last/Next run" dates are in the past even after a manual run, here are the three things you have to check:

1. The Certification Audit is "Locked" or in the wrong State

If a Certification Audit is already in a state of "In Progress" (perhaps from a failed job or a stuck process during the clone), it will not trigger a new run.

• Check: Open the specific Certification Audit record.

• Fix: Check the State field. If it's stuck in "In Progress" or "Work in Progress," try resetting it to "New" or "Draft" and then click Run Audit again.

2. Scheduled Job Queue (sys_trigger)

If the "Last run" date isn't updating, the background job that processes the audit might be stuck in the system scheduler.

• Check: Navigate to sys_trigger.list and search for Name contains "Certification Audit" or the name of your specific audit.

• Action: Look for the Next Action date. If it is in the past, the job is "queued" but the system isn't picking it up. You may need to delete that specific trigger record and then click "Run Audit" on your template to force the system to recreate a fresh trigger.

3. Domain Separation or User Criteria (If applicable)

Since this happened after a clone to Prod, check the "Run As" field on the Audit record.

• The Issue: If the Audit is set to run as a specific user who doesn't have access to the CIs in Prod (due to Domain Separation or ACLs), the audit will find 0 records.

• Fix: Ensure the Run As user is active and has the certification_admin or admin role.

4. The "Certification Schedule" vs. "Audit"

Check if you are running the Audit or the Certification Schedule.

• In the Certification Audit record, check the "Certification Filter" again. Click the "Preview" button on that filter record.

• Crucial Step: If "Preview" shows CIs, but the Audit Result doesn't, it confirms the Audit Script is failing. Check System Logs > Errors immediately after clicking "Run Audit" to see if there is a Null Pointer Exception or a Script Include error.

If this is useful, please mark it as helpful and accept my solution ...