Custom Metric > Collect Significance Count of Repeated Problem Entities

[jennieBYU]

I would like to provide a view for my operations center to see active problems. The operations center is managed and maintained by entry-level technical students and so I would like to provide some additional context of significance to help our operators better weed through the problem noise. One would potentially be a custom entity metric to trend problems it has been impacted by. Anyone have an idea how this could be accomplished?

[ChadTurner]

@jennieBYU can you expand on this a bit? I'm a little bit confused based off what was written. Are you looking to build a dashboard that outlines all of the active problems? Or are you looking to ensure that all problem cards are enriched to show related entities of the given problem card? 

[marco_irmer]

I know this isn't what you were necessarily thinking of with your original approach, but Dynatrace does actually provide guidance about how severe a given problem is based on the Davis event category. The documentation lists out the categories in order of most to least severe. This information might be useful when it comes to stacking the display of problems on a console.

Another approach, which admittedly would take more effort, would be to use a tagging scheme to your entities that denotes their "criticality" or some other dimension that is useful in determining what should be at the top of the list. You could then build a custom dashboard that shows the highest priority problems at the top of the list.

[jennieBYU]

This had more to do with, if the exact same problem affecting the exact same entities happened thirty times in a month or day or three times ever, so when our NOC sees the alert, it provides further context as to how frequently the exact problem occurs.