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
Article Comments
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
May, 2014 - Permalink
Please provide the screenshots, this might be an issue in the Trigger Settings, and seeing those might clear things up.
May, 2014 - Permalink
Screenshots can be found here: http://vatti-manhattangroup.com/images/trigger.png http://vatti-manhattangroup.com/images/stats.png
May, 2014 - Permalink
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.
May, 2014 - Permalink
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
May, 2014 - Permalink
The unit "mega" in the Trigger does not seem correct, it should be "MByte". Is this available?
May, 2014 - Permalink
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.
May, 2014 - Permalink
I set the number to 2097152 with no unit and still got no alert even though the value is consistently above 3.
May, 2014 - Permalink
It works fine here in several tests. Maybe try adding the sensor again and also try creating the trigger anew.
Jun, 2014 - Permalink
I setup a new sensor and trigger and it seems to be working as expected. Thanks
Jun, 2014 - Permalink
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.
May, 2014 - Permalink