John_King

That sounds like an issue with the trigger action. Does this happen for all configured alerts? That sounds like an issue with the trigger action. Does this happen for all configured alerts? No, I have 200+ identical alerts and most of them work fine. The only difference in any of the alerts is the node name.

I see those kinds of alerts on a daily basis and I can live with those. These have a short delay (usually 2-5 min) and are down for hours (ex. I currently have one down for an hour and a half now with no trigger commands sent) but the alert is showing triggered and I will receive the the reset commands when it comes back.

 Talked to Orion support. Apparently this is an isolated issue so it is probably some quirky setting on the server or user error.

 OK, I see where I am missing it. My alerts are Advanced Alerts. I did however drill down in the database and found that it reported it only sent one message. I just got off of a GoToMeeting with one of the techs at Solarwinds and we determined my problem was with importing alerts for an older 8.5 into 9.1, which normally…

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…

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…

 We have been having this problem since 8.5. We had a ticket open on the issue since it would cause the polling engine to stop and the service appeared to hang (with the splash screen frozen). The ticket was closed with no resolve, we were just told to wait till 9.0 came out or upgrade our equipment. In the next couple of…

I apologize, I should have read your previous post better. The reset condition is set to "Reset when trigger conditions are no longer true."

I see the same issue all the time I am also running 9.5 SP3 and seem to have issues with actions not triggering. In my case though none of the actions will trigger but the reset actions will. It's not the alert itself as I have 200+ identical alerts with only a node name difference between them and most will work fine but…

Do you mean the Trigger Condition or Trigger Actions tab? I can't seem to find the box your talking about.

That's all it needed to let the program run. I can now see calc when the program is called and the batch file runs correctly and the process terminates as it should. Thank you, thats the fastest I've had a fix for Orion yet.

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

These are the trigger actions, the bottom three are set for after hours (0-8 M-F, 17-24 M-F, 0-24 S-S). At one point I suspected they might be the issue, but the always worked for the reset actions and removing them did not fix the issue in this case. These are the reset actions that always execute

I shot you an email with a screenshot.

Here is my derivative of this, it may be useful to others. I added the IsDeleted field to eliminate routes that have been removed from the router. This came in handy when changing carriers for multiple sites, we could see when the old carrier routes were inactive and clean them up accordingly. SELECT Caption,…

It turns out there is some weird things happening to the alerts in the database and tech support is working on creating a patch for this problem.

In regard to your second problem I would suggest a secondary alert be created just for the escalation. You can copy the original and modify the time settings as needed. Set the Time of Day in the alert setting to the after hours so it will only trigger after hours. To get the e-mail make sure to set the Time of Day in the…

 Now that is seems there are quite a few fixes out are they all available through the update included in V9? We are looking at moving off of 8.5.1 in the next few weeks and was hoping I wouldn't have to find a dozen different patches to fix graphs, etc.

I found this elsewhere on the forum but can't find it again and want to make sure I can find this later. I put in an SQL filter on the resource as appropriate. You can set the values to whatever threshold you want and this disregards the discards value when sorting, though it will still show them. Top XX errors for Today…

Not so much a solution to the filtering as a work around but if you create a report in the report writer and add the report to your page, much like you would add "Nodes with Problems" it can also be filtered and it has the option to include (and filter through the report) the UDP fields. It gives you the filtering option…

You can use the following SQL to effectively remove the discards and only get the errors. Top XX errors for Today filter (InErrorsToday > 250) OR (OutErrorsToday > 250) Top XX errors for Hour filter (InErrorsThisHour > 250) OR (OutErrorsThisHour > 250)

 I am having a similar problem after upgrading to v9 I am recieving duplicate messages for every alert

I am currently experiencing those errors as well as a few others in some limited situations (alerts not firing for some nodes). They were found when I submitted a diagnostic to SW support. Have you had any luck in determining the cause/avoidance of these errors? Waiting on a DBA to take a look sometime next week.

 Opened a ticket on the issue. The execute external program will launch a process but it will never complete or show up except in Task Manager. We have tried different batch files from simple to complex and even calc.exe but with no luck on the advanced alerts.The basic alert still works fine with the batch files as well…