Grouping CI Classes on Reports

[Marques2]

Hello All,

I am creating report on the incident table to show incidents created over time, stacked by Configuration Item > Class. This was quite easy to do using the following report attributes:

Table: Incident

Type: Column

Group By: Class

Stacked: True

A requirement which I am trying to meet is to 'group together' the alike classes, such as classes which pertain to 'Storage' vs. having separate classes for Storage Area Network, Storage Device, and Storage Volume.

Is this a possibility within the report design? I have not been able to figure it out and hope that there's a way to do this so I can display the desired report on a homepage.

Any help is appreciated!

Thank you in advance,

-Marques

[Uncle Rob]

What makes it difficult is that there isn't a fixed # of tiers in the hierarchy, so you'll never know what class you SHOULD be displaying.

For example... my iPhone

Does it get classed under Mobile phones?   Phones?   Or hardware?  

[Marques2]

I'm with you on that!

It's more about the CI hierarchy than grouping the classes within the report. I guess that bigger problem is I'm trying to use a single report that encompasses classes from the Hardware hierarchy, Application hierarchy, Virtual Machine Object hierarchy, etc.

Glad you're following my struggle here though. I may not care for all the different server classes, I just want group all the servers. Same with the storage devices noted above. Reason I need it in a single report and stacked is because I want to give a holistic view of total incidents assigned to a support group, with an idea of what CI classes are associated with the incident. The report I have is just too granular, I need it brought up a level.

I know I just explained everything over again, but appreciate the response, Robert.

-Marques

[Marques2]

[Uncle Rob]

Its a shame the classes aren't records of their own... then you could just make a "reporting bucket" for each of the classes.

I suppose you could make it a property of the CMDB table itself... but then you've got to update ALL records with their reporting bucket and build rules to maintain it.
As my kids would say, "that's yucky poo poo"

... but it would also work.   :S