Performance Analytics Dashboard for Orphan relationships

[Vijay Ram reddy]

 we need to Create a platform analytics dashboard to take Data hygiene over time.
The first visualization will be a line chart that shows 2M orphan relationships.
Our goal is to decrease this count to zero but have historical record of the clean up. So how can i achieve this ..?

[Vijaya_Mnpram]

@Vijay Ram reddy 2M orphan CIs? or relationships?

The platform analytics dashboard work same was reports. The data source you use will be your table with filters.

What exactly is your ask? You need to make a line chart for 2M records?   

[Vijay Ram reddy]

@Vijaya_Mnpram - i have created a automated indicator, indicator source  on cmdb_rel_ci table and created a scheduled job which runs daily for now and once we clean up we change that to on demand or monthly once  all in PA , i have a  below dashboard showing line chart . i did all this because client wants historical data bcoz once we delete them we wont be able to see them , so historical data is needed to show management . Coming to your question we have 1.5 to 2 M orphan relationships in which parent CI's are missing in base CI table for various reasons . so i need to build a dashboard to show how many such relationships exists from last one year ,we are planning to delete them in batches not all at once , so everything has to be there in dashboard . Now im not sure below dashboard is good enough to capture all 

[Tony Branton]

A dashboard for identifying orphaned relationships already exists and can be accessed from the Quick Links on the CMDB Workspace home page.

The lists from this dashboard could be used in your own workflow for creating a task, adding descriptions of relationship records to worknotes in an activity stream as the orphaned relationships are removed.

[fknell]

Hi @Vijay Ram reddy ,

I would recommend using the Relationship Health Dashboard accessible from the CMDB workspace instead of building a custom Platform Analytics chart for orphan relationships.

Why this works for your use case

• The Relationship Health Dashboard already tracks orphan relationship counts and shows them over time, which gives you the historical trend you need while you drive the count toward zero.
• It is an OOB CMDB‑Health view, so you stay aligned with standard reporting and avoid duplicating logic.

How to use it

• Open the CMDB workspace → go to Relationship Health → use or clone the existing widgets into your own dashboard if needed.

• Ensure historical data collection is enabled for the CMDB Health indicators so you retain a long‑term trend even after you clean up to zero.

Hope this helps increase your CMDB health.