Retired Application Service and Business Application

[NidamarthiP]

Hi ,

Do we have to maintain relationship for retired Business Application and Application Services? If there is no any relationship for retired Business Application or Application services will it impact anything? Could you please provide your thoughts?

[SanjivMeher]

I think It is not a bad idea to keep the relationship even if the Application and services are retried. It would help in future during audits or while resolving past incidents. Any particular reason you would want to delete it?

[Mathew Hillyard]

Hi @NidamarthiP 

The first step is to see whether your organisation has any mandatory retention policies for such data, and whether you can archive this data if no longer in use. 

If you retain everything (so Business App to App Services to all their CIs) that is retired then in large CMDB this will bloat the CI Relationship table and slow down every query in the CMDB that utilises CI Relationships. In addition you will need to filter out retired objects in every CMDB query, report, visualisation etc. to avoid bringing in data that is no longer relevant. I've been there and it can become very difficult to manage.

Given retired data is unlikely to be updated I would potentially consider archiving so you retain the information but it doesn't affect the operational data.

I hope this helps!

Mat

[Carolyn Rast]

GM @NidamarthiP 

Data stewardship is key.  Retired CIs need to be archived or they will appear on dashboards and workspaces.

Bottom line - if you don't have data retention policies set up, you need to look at Data Manager and get them set up.  Once a CI is Retired then Data Manager will handle the archive and delete tasks for you.  You set policy and Data Manager does the work.

This is all theoretical - I am in the process of making this a reality - I hope I haven't over sold the solution!