Notifications

149 views

Issue

Overview


Please review our documentation to know more about CMDB health jobs: Domain separation in CMDB Health.

After CMDB health jobs are completed successfully, we can see health result records are shown with the Same CI, Same Task number and for the same metric in different domains. 

Cause


Since scheduled jobs are not domain separated currently each Dashboard job run finds health results and scores for all domains together.

As the job loops through each domain, it creates a separate set of cmdb_health_result records based on the rules in that domain (orphan/staleness/recommended). Refer to screenshot below.

This means for a CI there might be one cmdb_health_result record for each domain the CI is visible in

There is an ACL on the cmdb_health_result so that a user can see the cmdb_health_results only for the domain of the session it is logged into.

We have an ACL which is trying to hide them based on the Users Domain. If I deactivate it, I can see all domains:

https://<instance-name>.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=dfac9f11d7011200c1ed0fbc5e6103b8

In this ACL, it's calling a script include which is allowing to show the records as per users specific domain:

https://<instance-name>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=be7d6fb4d72212004b2fa5f75e610333

 

 

Article Information

Last Updated:2019-08-02 21:08:26
Published:2019-04-25
Health Result _ domain seperated_ Env.jpg