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

In dependency case, application monitoring also should be unreachble state

Hi,

we created the dependency and which is working fine and node went to unreachable state but some node's application monitoring template is not going to Unreachable state and we are getting alert for application down.

IF node is unreachable state then all node's application also should be in unreachable state,

suggest for this how we can manage these are thing so not get the further alert.

Find more posts tagged with

node's dependecny

Accepted answers

All comments

AlexSoul

It is possibly issue with polling frequency. If application is being polled every 10 minutes and your alert is checking for conditions every 1 minute, then I believe you will have this issue where application didn't quite yet picked up on a new state. I am not 100% sure though and this might need so resting to confirm exact behaviour

aLTeReGo

This condition can occur when the Application Status is polled before the node status, but should resolve itself after the next poll. E.G.

1. Node is polled as "Up"

2. Node fails

3. Application is polled as "Down" (in Orion Node is still up until next polling interval)

4. Node is polled as down

5. Application status is updated to 'Unreachable'

If this is not the behavior you're seeing, then please open a case with support.

krishnamishra0786

Thanks Alex for quick response,

What I observed that event id based application template is not being

covered in dependency, and rest of like wmi polling services are auto

unreachable

In screen shot u can see some are auto unreachable and some are triggering

alert because same is showing down

krishnamishra0786

Hi,

Suggested condition is working fine, but what i am observing where event id based monitoring template is applied in node, those template only not going in unreachable state and rest are auto unreachable, you can check the screen shot which i attached.

See some are in unreachable states, DFSR and BSOD both are event based monitoring template.

aLTeReGo

Do the 'Down' applications not change to 'Unreachable' after the next polling interval?

krishnamishra0786

Yes, Not changing to Unreachable after next polling..

AlexSoul

well, this is odd. What exactly is a feature request? I believe all dependencies and apps assigned currently to node must be rolled into Unreachable state. If "by design" this is not the case - I would like to know about it as well.

As a side note - from the alerting perspective I would always include additional filters to not trigger alerts for apps, volumes, interfaces, etc should the node itself being Down or Unmanaged, but this obviously has no effect on graphical representation of object states in UI

krishnamishra0786

Hi Alex,

could you please share any snapshot that can help us on bellow your comment. based on we can create the further additional filter in alert..

(I would always include additional filters to not trigger alerts for apps, volumes, interfaces, etc should the node itself being Down or Unmanaged)

AlexSoul

Here it is:

krishnamishra0786

Yes exactly Alex, i used the little bit different and also i late here to reply you.

I used the Node is equal to up condition only in application alert where rest condition would be suppress automatically like - node down, node unreachable, node unmanage.

now working perfect and awesome.

thanks