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

Incorrect Advanced Alert Test Nodes

We are running Orion 8.1.0 and are getting ready to switch it into production. I have the majority of our network nodes already alerting and working I just need to set alerts for our core gear and Cisco firewalls. Until recently I was not able to use the Advanced Alerts Test Button (hour glass) but after finding the work around it appears that the Advanced Alerts simply do not alert on the right nodes. I have tried running my older alerts using the test button and get the same problem. I will alert on a core or firewall node (with a rule to eliminate other network nodes) and receive an unrelated network node. When we drop the physical connection the alert works as it should, but the Test button does not give the same results. Obviously I can't drop my core gear, so how do I test my Advanced Alerts? Has anyone else had a similar problem?

Find more posts tagged with

Accepted answers

All comments

mark_wiggans

this is a known issue for 8.1 and only affects the Testing of the Alert for the
Advanced alerting and does not affect the actual alerts. It has been fixed in 8.5-

John_King

Is there some kind of work around for this in 8.1?

mark_wiggans

The work around is to test using the Advanced Alerts Manager not from the system mgr. Also you can set-up a test to receive a text file and then verify if any text is seen in the alert log.

John_King

The alerts I am testing are being tested from the Advanced Alerts Manager the System Manager Alert testing does not work in 8.1. I'm wondering why the node that I receive my alert for and the one I'm testing are not the same. Example Testing node: FW-CO-DENVER Alert Message(e-mail): RT-KS-NEWTON

The alert retains my formating and variables but is just for the wrong node.

SteveSW

The test fire button only runs the alert actions. It is not affected by the trigger condition configuration.

It is likely that you are selecting a node to test fire with that does not support the alert type for the selected alert. For example, if you are setting up an application alert but select a node that does not have any applications defined the test fire system will find another node with acceptable information and resolve variables using that node instead. So your alert message may show you information about different nodes than you selected because it is just trying to show you what the alert actions would look like if the alert was triggered. This is not cause for alarm and does not indicate that an alert is configured incorrectly.

John_King

Thanks for you post. I originally thought that was the case but in testing multiple nodes on different alerts I always get the same results in my reply.

I have one alert that monitors all Serial0 interfaces on our Cisco routers. This alert has been in production for 3+ months and works flawlessly. When I test this alert using the Advanced Alert Manager it produces an incorrect node other than the node I am testing.

With the new alerts and different requirements I get the same thing. Even if I specify the alert for 3 Nodes and to only alert on those 3 nodes I will get an incorrect node when I test it using the Advanced Alert Manager (usually not one of the 3 nodes)