Displaying Cause of Component Events

Appreciate the answers. These solutions are a lot of legwork and I'm not sure they address what I'm after. Also, I'm not using AppInsight at all.

If MSSQLServer was using 98% memory, it would show on the component page like my screen shot (note, i wasnt able to reproduce a problem for the shot).

What I'd like is to show this detail on say, the home page, but there is no resource for components that will show that. I can add the "Applications With Problems" resource, which is what I'm currently using, but it ONLY tells me a component is Warning or Critical, etc. What it doesn't do is show me the memory use is high, which is the cause for the app being critical or warning. I've never understood why a monitoring system like Orion can't do this out of the box. Seems like something as simple as a "Components With Problems" resource that would actually show you this might help.

It's starting to look like without some heavy customization of alerts, or some complicated SQL query this is just not possible. Mind boggling considering this was an annoying issue five years ago, and still is.

Appreciate the answers. These solutions are a lot of legwork and I'm not sure they address what I'm after. Also, I'm not using AppInsight at all.

If MSSQLServer was using 98% memory, it would show on the component page like my screen shot (note, i wasnt able to reproduce a problem for the shot).

What I'd like is to show this detail on say, the home page, but there is no resource for components that will show that. I can add the "Applications With Problems" resource, which is what I'm currently using, but it ONLY tells me a component is Warning or Critical, etc. What it doesn't do is show me the memory use is high, which is the cause for the app being critical or warning. I've never understood why a monitoring system like Orion can't do this out of the box. Seems like something as simple as a "Components With Problems" resource that would actually show you this might help.

It's starting to look like without some heavy customization of alerts, or some complicated SQL query this is just not possible. Mind boggling considering this was an annoying issue five years ago, and still is.

Yeah, it's a pain point and has no easy solution because each type of component has really widely different situations that can cause them to display as critical, and nothing built in tracks them for us.  So at this point the best that can be done is to build up a mess of SQL/SWQL to test for each scenario and basically say "if the component is a process, check these 6 things, if it's a script check these.