What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Proper Last Windows Update notifications

Votes:

0

Your Vote:

Up

Down

We are using the new Last Windows Updated feature for our Desktops and Laptops and we have setup notification if the value is greater than 30 (days). We have also set it up to check during business days and hours only. Some problems, or annoyances, is that it will alarm when the trigger threshold is exceeded, but also when it drops below the threshold. Meaning it will come in red when the threshold is broken and will also come in red when the trigger is below the threshold. Shouldn't the below threshold notifications be green "go to go"? Also, we have a lot of alarms sitting in the alarms page that are form systems it could not reach. It would be nice if we could configure it not to alarm if it couldn't reach a system after a certain time period. Only alarm if it couldn't reach a system say after 7 days or something. Otherwise we have all these alarms for mobile users that really aren't alarms. Takes away from viewing or noticing actual alarms. Thanks.

notifications windows-update-status wmi

Created on Jan 2, 2014 10:07:00 PM by  itacquisitions (0) 1



3 Replies

Votes:

0

Your Vote:

Up

Down

If you use the channel limits to set up a limitation on the Days Ago channel, it should only go into an error status when that value is above what you define. Make sure that you only define the upper limit and it should work correctly. If this is still alerting, make sure to check the alert to see what is causing it, it may be something else that's causing the alert.

With regard to devices that are disconnected from the network, there is really no way to avoid them being in an alarm state other than to use a schedule to pause them or pause them manually. You could also have the sensor pause itself or auto-acknowledge using a notification and executing an HTTP action that uses the API like what is described in the article here

Created on Jan 6, 2014 1:57:05 PM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Actually, my mistake. It doesn't error for both (red), it's green for both. So if the threshold is exceeded it notifies green and states the threshold was reached. Then if it clears or drops below it sends a green notice that threshold is not reached. We are on version 13.3.4.2557 and the notification is setup as follows:

Threshold Trigger - When Primary channel is Above 30 for at least 5 seconds perform Email to Admin - When condition clears perform Email to Admin

We are only using triggers for this object and not inheriting any. This is the only one. Thanks.

Created on Jan 6, 2014 5:20:30 PM by  itacquisitions (0) 1



Votes:

0

Your Vote:

Up

Down

Setting the threshold trigger like this will not make the sensor go into an error status. If you want to define when the sensor should be in an error status, please set up channel limits for the channel and then the sensor will go into an error status when that limit is hit.

Created on Jan 8, 2014 11:49:27 AM by  Greg Campion [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.