Issue
How should the relationships with that CI be handled when i","articleBody":"
Best Practice in handling relationships of a retired CI
Issue
How should the relationships with that CI be handled when it is retired in the ServiceNow CMDB?
\r\nThis article advices on the best course of action, including whether to remove or maintain the relationships as-is.
Resolution
There isn't a "typical" retirement process that everyone follow, so this isn't automated or integrated into the platform.
\r\nNote: When the CI's lifecycle is complete, Discovery will not automatically destroy these Relationships; instead, custom BRs must handle this
However, it is recommended to keep an eye on the data and eliminate unneeded relationships to preserve integrity.
For example:
\r\n- The relationships to the retired CI MUST be deleted/removed if an application service has multiple servers, one of which is a retired CI.
- There would be no active relationships if all the servers in one application service were retired, thus retaining or deleting them would have little effect. However, we continue to advocate for data cleansing.
Loading...
Loading...