- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-27-2019 07:42 AM
I need to show the amount of certain type of entries for each "Child" in the cmdb_rel_ci table. The breakdown A on these elements has more than 4000 elements. In order to use this breakdown properly I thought of creating a breakdown relation to use breakdown B before and get the number down to a small fraction of 4000.
Now here comes the tricky thing. Both breakdowns have a mapping on the Child field of this table. Breakdown A uses the reference field itself and breakdown B uses a reference field of the Child. However, since breakdown B only works for certain types of ci, I had to script the breakdown mapping.
While creating the breakdown relation i can not work with the scripted breakdown mapping and am stuck.
The idea is to use the dashboard breakdown sources to narrow down with breakdown B and then display a breakdown widget using breakdown A. Is there another solution to my problem which I am not seeing? Or is my only option to dial up the com.snc.pa.scorecards.abs_max_breakdown_elements value? In the end I would still use multiple levels of breakdowns and the amount of breakdown A elements with data for each element of breakdown B with data in them would be much smaller than 4000.
Is it recommended to fiddle with com.snc.pa.scorecards.abs_max_breakdown_elements? What are possible side effects or the worst outcomes. Performance wise?
Solved! Go to Solution.
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2020 12:52 AM
I found the answer to the first and more important part of my question now.
It seems I did not understand how the breakdown relations can be built (connecting breakdown elements with a completely unrelated table). Using a different table I was able to find the information that connects the elements from the two breakdowns and it works as it should now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2020 12:52 AM
I found the answer to the first and more important part of my question now.
It seems I did not understand how the breakdown relations can be built (connecting breakdown elements with a completely unrelated table). Using a different table I was able to find the information that connects the elements from the two breakdowns and it works as it should now.