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

Application Monitor availability when using unmange

Hello,

We are currently running APM 3.1 and have noticed an issue when unmanaging nodes with applications. I noticed that when we unmanage an application directly, or indirectly by unmanaging its node, that the status for the application shows as "unmanaged" but there's also an associated event both when the application is unmanaged and remanaged that it is in an unknown state, and this is fairly drastically affecting our uptime percentages.

We've also noticed that alerts we have associated with applications are getting triggered because of this. We have these alerts tied to down or unknown state, since they fire off scripts to restart said applications.

Has anyone else run into this, and are there any known work arounds or fixes in the works?

Thanks!

Find more posts tagged with

Accepted answers

All comments

FormerMember

Shameless bump. This is kind of a hot button item for us right now as we are trying to run uptime reports to see if we are meeting SLA requirements and when all of our scheduled down (unmanaged) time is counting against our percent uptime, its kind of a big deal.

Are we unique in seeing this issue, or has anyone else experienced this as well?

byrona

Hrm, I definitely can see your problem and think that SW should use an "Unmanaged" status in place of "Unknown" but I also understand the reasoning behind using "Unknown" status in this case.

I have my alerts only set for "Down" status to avoid the problem with the "Unknown" status. What I have found is that with at least one service monitor using SNMP is that it very often will get reported as "Unknown" for one or two polling cycles and then will come back and during this time the process is running just fine. Do you ever experience this?