What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

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

IIS Application Speed Alert

Votes:

0

I have an IIS Application Sensor where I alert on bytes Sent > 4mbps. The sensor is scheduled from 5am-midnight. At the same time the IIS server is scheduled to start IIS at 4:59am. The probem I am having is that every morning I get an alert that the bytes sent are > 4mbps but they are 1mbps or Unknown (I assume because the sensor just started). How can I stop the sensor from sending the false alert? Thanks

Sensor History (from the alert)
5/20/2014 5:02:00 AM Up, 1 #/s
5/20/2014 5:01:54 AM Up, 1 #/s
5/20/2014 5:01:53 AM Unknown, PC OK
5/20/2014 5:01:53 AM Up, 1 #/s
5/20/2014 5:00:01 AM Unknown, No data since 5/19/2014 11:59:59 PM
5/20/2014 5:00:00 AM Paused, No data since 5/19/2014 11:59:56 PM
5/20/2014 5:00:00 AM Unknown, No data since 5/19/2014 11:59:56 PM
5/20/2014 12:00:01 AM Paused, Paused by schedule
5/20/2014 12:00:00 AM Paused, Paused by schedule
5/20/2014 12:00:00 AM Paused, Paused by schedule

iis prtg wmi

Created on May 20, 2014 3:01:48 PM

Last change on May 21, 2014 9:14:12 AM by  Torsten Lindner [Paessler Support]



Best Answer

Accepted Answer

Votes:

0

It works fine here in several tests. Maybe try adding the sensor again and also try creating the trigger anew.

Created on Jun 3, 2014 7:56:25 AM by  Torsten Lindner [Paessler Support]



12 Replies

Votes:

0

Hello,

thank you very much for your KB-Post. Can you please upload some screenshots showing the definition of the Trigger on this sensor, and the actual live / raw values then after this restart? Thank you.

best regards.

Created on May 22, 2014 8:51:56 AM by  Torsten Lindner [Paessler Support]



Votes:

0

I'll try to add screenshots but here is the trigger definition

Speed Trigger

When Bytes Sent channel is Above 4 /second for at least 600 seconds perform NOC When condition clears perform no notification

And here are the values after the start

Date Time Bytes Received Bytes Received Bytes Sent Bytes Sent (volume) (speed) (volume) (speed) 5/22/2014 5:00:04 AM 0 MByte 0 Mbit/s 0 MByte 0 Mbit/s 5/22/2014 5:01:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:02:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:03:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:04:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:05:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:06:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:07:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:08:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:09:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s 5/22/2014 5:10:04 AM < 0.01 MByte < 0.01 Mbit/s < 0.01 MByte < 0.01 Mbit/s

Created on May 22, 2014 4:21:25 PM



Votes:

0

Please provide the screenshots, this might be an issue in the Trigger Settings, and seeing those might clear things up.

Created on May 22, 2014 4:41:42 PM by  Torsten Lindner [Paessler Support]




Votes:

0

It's an issue in the Trigger, please be aware that you need to calculate a conversion in the trigger because there it is Bytes / second, so you need to convert the Threshold of 4 MBytes / second into Bytes / Second (4194304) and then enter this value.

Created on May 23, 2014 8:02:47 AM by  Torsten Lindner [Paessler Support]



Votes:

0

I changed the trigger and now it doesn't alert at all... Even when the condition should have been met. Note that I change the numbers to force the alert. http://vatti-manhattangroup.com/images/stats2.png http://vatti-manhattangroup.com/images/trigger2.png Thanks

Created on May 29, 2014 2:35:06 PM



Votes:

0

The unit "mega" in the Trigger does not seem correct, it should be "MByte". Is this available?

Created on May 29, 2014 2:58:53 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Options (besides blank) are kelo, mega, giga.

Created on May 29, 2014 3:04:12 PM



Votes:

0

It's too high now. Please try the converted value I've noted above with no unit set for the Trigger. This is most likely a conversion error.

Created on May 30, 2014 1:12:24 PM by  Torsten Lindner [Paessler Support]



Votes:

0

I set the number to 2097152 with no unit and still got no alert even though the value is consistently above 3.

Created on May 30, 2014 4:26:36 PM



Accepted Answer

Votes:

0

It works fine here in several tests. Maybe try adding the sensor again and also try creating the trigger anew.

Created on Jun 3, 2014 7:56:25 AM by  Torsten Lindner [Paessler Support]



Votes:

0

I setup a new sensor and trigger and it seems to be working as expected. Thanks

Created on Jun 4, 2014 1:44:01 PM




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.