How to get data cmdb ci upstream and downstream data in audit history

vamshi2
Tera Contributor

Hi Team,

 

audit history is not capturing data related to relationship as shown below 

 

vamshi2_0-1753341051700.png

 

 

3 REPLIES 3

Naveen20
ServiceNow Employee
ServiceNow Employee

Is it not getting captured in cmdb_rel_ci table with audit history

Harish Bainsla
Kilo Patron
Kilo Patron

Hi @vamshi2 cmdb_rel_ci table: This table defines the relationships between CIs stored in the cmdb_ci table. Each record in cmdb_rel_ci represents a relationship between two CIs, indicating, for example, that a specific server "hosts" a specific application

for more understanding check below link

https://www.servicenow.com/community/developer-forum/cmdb-data-model-amp-relationships/m-p/3083472#:....

https://www.servicenow.com/community/cmdb-forum/enable-audit-history-for-upstream-and-downstream-rel...

if my answer helps you mark helpful and accept solution

 

AJ-TechTrek
Giga Sage
Giga Sage

Hi @vamshi2 ,

 

By default, the Audit History on a CI (e.g., cmdb_ci_computer) only tracks changes to fields on that specific record.
Relationships (like upstream and downstream) are stored as separate records in the cmdb_rel_ci table, so they’re not audited directly on the CI itself.

 

Solution capture and view relationship changes -


1.Enable auditing on the cmdb_rel_ci table
* Navigate to System Definition → Tables.
* Search for cmdb_rel_ci.
* Make sure:
* Audit = true
* Audit changes = true
This ensures inserts, updates, and deletes of relationship records are captured.

 

2.View the audit history for relationships
After enabling auditing:
* Go to History → Audit History on the relationship record itself (not on the CI).
* Or:
* Navigate to the cmdb_rel_ci table.
* Filter for records related to your CI (Parent or Child field contains your CI).
* Open the history from there.


3. Build a related list or report
If you want to see relationship changes directly on the CI:
* Add a related list to show audit records from sys_audit where Document = related cmdb_rel_ci records.
* Or build a report that pulls audit data for the related relationship records.

 

4. Consider using CMDB Health Dashboards
For better visibility into relationship integrity, use the CMDB Health dashboards which track:
* Completeness (missing relationships)
* Correctness (invalid relationships)
* Compliance

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 
Thank You
AJ - TechTrek with AJ
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community MVP 2025