Is it possible to set monitors or rules to only fire during certain hours?

I’ve recently installed the latest Orion MP from Solarwinds and I’ve noticed a ton of “Orion Response Time Alert” alerts as well as others that happen predominantly during backup hours. Is there a way to supress events for this rule (as well as others) to reduce the noise? I really don’t want to have to put everything in maintenance mode throughout the entire night every night as I’d like to know if critical services really are having issues. I just don’t need hundreds of these warnings killing my views.



1 Like

Have SCOM monitor your critical services via synthetic transactions and only look at SolarWinds data if the synthetic transactions shows a slow response time or fails.

Thanks Wilson. I’d rather not reinvent monitoring though by having to create new transactions. I like what the MP is giving me but just want to have them go silent during the backup window.

Hi Gary

Yes; but you need to edit the code. I’ve given a very brief example here of building a powershelgl monitor with business hours and match count.

Part 1 – The PowerShell –

Part 2 – The Data Source and Probe –

Part 3 – The Monitor Type –

Part 4 – The Monitor –

Part 5 – A diagnostic task to view all the folders in the top level folder –

Part 6 – A recovery task to delete all the folders in the top level folder –

There are a number of ways to do it and the above is just my personal preference. It allows monitors to go unhealthy --> healthy out of hours but not healthy --> unhealthy by putting a scheduler filter on the unhealthy workflow.

If you didn’t want the monitor to run at all then you could put the filter on the underlying data source.



Well, my thinking is that you shouldn’t need to look at your SolarWinds data unless there an issue with your app. After all, your Solarwinds data is simply a means to an end, right?
At the end of the day you shouldn’t care about that data unless there is an actual impact to the service or app irrespective of backup windows…so I am thinking you should start from the end-user perspective first… and work your way backwards from there. Setting up a script to put those particular alerts in maintenance mode during backups is probably the best way clean up your views…while relying on the synthetic transaction to give you visibility to an end-user impacting service degradation/outage even if it occurs during a backup window.