solarwinded

Yes that is correct

We already have that setting configured with the FQDN and what I posted is what it outputs as. We are on Orion 2017.3.5 SP5 with SAM 6.6. Please make this available again for voting

Thanks. That is definitely an improvement but it will definitely still be a bear to find a specific node when we monitor several thousand

Thanks Alterego, that is a really good idea. I will give it a try

Thanks for the reply AlterEgo. I have tried that and the alert criteria doesn't appear to work. Can you please explain how it works? When I enabled it, all it seemed to do was alert every minute and then reset itself, after following the KB here: Configure alerts for other DNS types I contacted Orion support and they…

My scenario is a DNS update script, that only needs to run when a failover event occurs. Running a DNS script to update the DNS entry of your current Orion server every 1 minute seems excessive, but I am not sure how AWS Route 3 works

Thanks for looking into this. I will try to get the upgrade scheduled

Hello LadaVarga, thanks for the reply. Can you explain what the trigger conditions are and how that signals only in the event of a failover? It looks like it is just stating that a pool member is equal to "MainPoller" and the Pool ID is not empty. Wouldn't these conditions be true at anytime regardless of which HA server…

2017.3.5 SP5 and SAM 6.6.0

It looks like I got it working. Step 3 is absolutely wrong and should be updated. I think what I couldn't picture at first was that there would always be an "active alert" for whichever HA node was active. I have modified the severity to "Notice" since we don't use that for any other alerts so we can filter it out. I have…

Thanks I will give it a try and let you know

Bump. This would be extremely useful to have

Thanks that did the trick for me

Nice job finding that jvogel! I'm not sure that will work for us though, as we use the PowerShell transcription. It's too bad something like logging script output causes an alert to go off.

Has anybody found a resolution to this issue? I am having the same problems except we are on the latest release! 2018.2 and SAM 6.7 on Server 2012 R2

Another way to make the alerts seamless for monitoring Windows Services is to use Component Type is equal to 9. 9 is for Windows Service Monitor components. So if you want to separate out your templates, you can still utilize one alert for services (and other types of components.) A list of component types with…

Looks like the custom property is much cleaner for the alert trigger and is working great. Thanks all for the help!

Thanks sirpaw. I'll test it out and see how it goes too. See my above post for some background on what I want to accomplish. It didn't get approved until this morning. This may do the trick!

Thanks for the reply. Let me try to describe what I want to do. I just inherited this project and there are currently https monitors for some sites we have. The way the alert trigger logic is currently setup is: If Application Monitor for Site1 is Down OR If Application Monitor for Site2 is Down OR etc...30 times for 30…

Nevermind, just found this thread that explains there is an existing issue. I guess we have to set the preferred polling method to Agentless PowerShell output

I am having the same issues with some of my PowerShell script monitors as well. Anyone have any suggestions? We are getting false alerts for these everyday Running on Orion 2018.2 and SAM 6.6.1