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

An App mon question...or three

Hi all,

I have a question or two about the app mon. First, is there some way for me to troubleshoot why i am may be receiving application down errors even when the app is known to be up on a specific host? I have two linux hosts that are running httpd and i know its up. strange thing is that when i used the old application monitor (pre apm) it judged the apps correctly and reported they were up.

Along those same lines, when I attempt alerts on in APM-Application "down" is not a status that I am allowed to choose. Only "up". someone suggested that I just type in down, which I did but when I recevie an alert it states the status is "unknown". What am I doing wrong?

it seems like i had something else..hmm..oh well, its left me.

TIA,

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Is APM incorrectly reporting that Apache the process is down via SNMP or do you have a HTTP/s port monitor or user experience monitor that is reporting down for that web server?

rhltechie

hi,

sorry, should have included that. its an snmp monitor for the httpd service.

josh.clark

There is a bug in the SNMP Process Monitor hat will cause it to fail when there are many instances of a process. This normally occurs on Linux boxes since servers like Oracle and Apache fork new processes for each new connection. This bug should be fixed in SP2.

The drop down in the Advanced Alerts dialog shows you all the values that are currently in the database. If everything is "up" you'll only see "up". BEcause of the bug described above, we don't know the state of the monitor - it may be up or it may be down. Since we don't know either way, we mark the moniotr as Unknown.

You can change your Alert to use "Status not equal to Up" to get both down and unknown events.

rhltechie

this makes sense...i do know that i have a very large number of the httpd instances running. When can we expect a fix for this? Alerting on unknown is not an option for me and the service is always "unknown". It's never been anything other than.

FormerMember

We are still working on an SP2. Weeks, not months is the most precise estimate I can give you at the moment.

rhltechie

great, thanks.