Orphaned Relationship Health Metric & CMDB Remediation

[Vlaho Djurkovic]

Hello,

We have a requirement to ensure that orphaned CI relationships are managed. The OOB health metrics are capable of detecting orphaned CI relationships; however, there does not appear to be a way to create a CMDB Remediation record for these. It appears that all the functionality located in CMDB remdiations deal with the configuration item, but not the relationship.

We are currently using stale CI remediation to set stale ci's to retired (cannot be deleted due to business data retention policies). I am looking to use the same functionality in order to keep the cmdb_rel_ci tables clean. Is this possible using CMDB remediations or am I relegated to creating a custom business rule or scheduled job to achieve this functionality (operation support nightmare)?

Thank you,

Vlaho

[Rim]

any solution found? I am looking at the same, especially after I found out that discovery creates a bunch of orphan relationships...

[emir]

Can you please explain, what exactly you're trying to achieve? CMDB_REL_CI does not have a status field. As long as the CI pair exist in the system, it is a good relationship and should be kept.

You can either delete the relationships (since they are orphans) or archive them. This is for when at least one out of the pair is no longer in the system.

See this post for more info.

[Rim]

Orphan relationship when one of the relationship CIs in the pair is missing. Normally this would not happen if you manually maintain cmdb and never delete CIs. However, when we started discovery, orphan relationships started to show up. For pretty much all the remediation, you can configure ServiceNow to create tasks for responsible teams to act on it. But this is not the case with orphan relationship remediation, at least I cannot see this option in Madrid.

[emir]

What do you want to achieve in the end?

Whoever gets the task assigned will not be able to find the CI, and even if they do, the pair is no longer in a relationship as Discovery didn't find it. So fixing the relationship would be wrong.

If the CIs are still in the relationship, then on next Discovery run the system should make another record of the relationship between the two Cis if it cant find a match.

Maybe you can provide some examples so I better understand the issue.