Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

APM 4 Anomalies & Quirks

Just want to get these out there and find out what other people are seeing / thinking.

When viewing the last 25 application events under the APM tab - Critical events are pink; Warning events are yellow and Up events are green. When viewing the last 25 events from the NPM Summary tab - Critical events are pink, Warning events are yellow, BUT Up events are green or BLUE?

Why are components marked as UP after being Critical or Warning? Should they be marked NORMAL? Only services or counters that can't be read should be marked UP and / or DOWN. No?

After playing with APM for a few months, I think we need a true application level grouping. Right now, for example, if we add various Exchange templates, each template appears as it's own app. That's not the case. When we want to know the status of an app, we want all the templates to factor into that status. At the least, all Exchange roles should roll up under a single role. For instance, the newly delivered Exchange templates (which are great BTW) are qualified by having the words "Basic" or "Advanced" in the titles. But this shows up as two different applications under the Summary screens. ACK! It's the same app!

When a component goes into alert, it generates two events, one for the component and one for the application monitor. This is counterproductive in our view, as there is only one event. Either generate an event on the component or on the app (with the component appended to the message details, so it still shows up on the event summary) but not on both. Or at least give us the option.

Anyone else that thinks these suggestions would be useful, please comment.

Find more posts tagged with

apm_4.0.2

Accepted answers

All comments

byrona

When viewing the last 25 application events under the APM tab - Critical events are pink; Warning events are yellow and Up events are green. When viewing the last 25 events from the NPM Summary tab - Critical events are pink, Warning events are yellow, BUT Up events are green or BLUE?

I agree, a more consistent color scheme would be good, or at least an explanation behind the thought of the current system.

Why are components marked as UP after being Critical or Warning? Should they be marked NORMAL? Only services or counters that can't be read should be marked UP and / or DOWN. No?

I agree, this is confusing. I think the reason behind the current functionality is because UP is used as the status to show something is NORMAL.

After playing with APM for a few months, I think we need a true application level grouping. Right now, for example, if we add various Exchange templates, each template appears as it's own app. That's not the case. When we want to know the status of an app, we want all the templates to factor into that status. At the least, all Exchange roles should roll up under a single role. For instance, the newly delivered Exchange templates (which are great BTW) are qualified by having the words "Basic" or "Advanced" in the titles. But this shows up as two different applications under the Summary screens. ACK! It's the same app!

The grouping is this way because of what you are looking at. You are looking at "Applications", not Application Templates. Once a template is assigned to a node it becomes an Application. To accomplish what you refer to as "true application level grouping" you can use the new Group functionality in Orion.

When a component goes into alert, it generates two events, one for the component and one for the application monitor. This is counterproductive in our view, as there is only one event. Either generate an event on the component or on the app (with the component appended to the message details, so it still shows up on the event summary) but not on both. Or at least give us the option.

This is configurable by you. I turned off Application alerts and choose to only use Component alerts. I would like the option to suppress alerts from the alert view so that the alert action could take place without it appearing in the alert view. This would help keep that alert view from getting cluttered with things that I don't need in there.

This is my $0.02 on your notes, hope you find this feedback useful!

jspanitz

I love the forums because I learn something new all the time....

The grouping is this way because of what you are looking at. You are looking at "Applications", not Application Templates. Once a template is assigned to a node it becomes an Application. To accomplish what you refer to as "true application level grouping" you can use the new Group functionality in Orion.

Hmm, agreed that the new Group functionality would work, but that leaves the Web interface still displaying a mess. I'd argue that we need this app grouping in APM.

This is configurable by you. I turned off Application alerts and choose to only use Component alerts. I would like the option to suppress alerts from the alert view so that the alert action could take place without it appearing in the alert view. This would help keep that alert view from getting cluttered with things that I don't need in there.

Is this done through the Alerts functionality or is there some other place to turn this on and off? I don't see anything in the Web interface.

Thanks, your feedback was very helpful - John

byrona

Is this done through the Alerts functionality or is there some other place to turn this on and off? I don't see anything in the Web interface

You need to log on to your primary Orion system and launch the Advanced Alert Manager application. This is where the power of Orion lies, you can define your alerts for pretty much anything.

Hmm, agreed that the new Group functionality would work, but that leaves the Web interface still displaying a mess. I'd argue that we need this app grouping in APM.

You can modify the view so it doesn't show the mess that you are referring to. All views in Orion are completely customizable. You can also create view restrictions; for example you can create a view that only shows applications with the word "Exchange" in them (I think SolarWinds may have this one already built by default in the system). I realize that this doesn't give you exactly what you are looking for but it does clean things up a bit.