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

How to schedule an Application monitor to poll once or twice a day

mikegale

I've got several log monitors that only need to run at a particular time. What is best practice for this type of alert?

- add the time to the script so that the app reports "UP" any other time

- use the Schedule Unmanage utility (alert will be unmanaged for 95% of the day)

Thanks for y'alls input

Michael

Find more posts tagged with

Accepted answers

mikegale

I did not use the Unmanage Utility in the end. I added some code to the powershell scripts so it only alerts at certain times.

Scheduling Powershell Component Monitors

All comments

bkyle

I would use the Unmanage utility. This will give you polling for only the times you need.

mikegale

It would give me the correct polling times but the rest of the time it won't be green on the console. Wouldn't it be nicer to have the application appear "UP" when it's not actually failing?

BWB8771

Have you found how to do this? I'm interested in doing something similar, but only enable monitor for a specific time span of the day.

bkyle

Did the Unmanage utility work?

mikegale

I did not use the Unmanage Utility in the end. I added some code to the powershell scripts so it only alerts at certain times.

Scheduling Powershell Component Monitors

adamlboyd

mikegale I'm a firm believe in collecting data. If you collect the data you can then see a trend that the customer/line of business may not have noticed. This is the difference in reactive monitoring vs. proactive monitoring. Now some people may not have a need for that, but having the data and not using it vs not having it is my mindset here. In addition to collecting the data you can then setup an alert to trigger at any time even if the component is up. With the web alerting now you can also set a custom status so you have a win for everything.

But like you said you can do your dateTime checks within PowerShell so during your out-of-monitoring hours you can return a statistic value and message with the correct data and with an exit code of 0. But within monitoring hours you can still return the same statistic value and message with the appropriate exit code.