Quantcast
Channel: THWACK: Message List
Viewing all articles
Browse latest Browse all 20396

Utilization Alerts Will Not Repeat (Not Resetting?)

$
0
0

Ultimate goal: Monitor all the switch ports (interfaces) in our network that connect to our MPLS WAN service to assess WAN utilization metrics.

Trigger Condition

Trigger Alert when any of the following apply

     Interface ID is equal to 1     {I wish I could add a comment here so I know what '1' refers to}

     Interface ID is equal to 161

     Interface ID is equal to 219

     Interface ID is equal to 216

     Trigger Alert when all of the following apply

          Average Xmit-Recv Percent Utilization is greater than 90

Do not trigger this action until condition exists for more than 1 seconds

Reset Condition

Same as above except Utilization is less than or equal to90

Do not reset this action until condition exists for more than 10 minutes

Trigger Actions

Send E-Mail...

General

Alert Evaluation Frequency: Check this Alert every 1 minutes

 

To test this Alert I tried ridiculously low numbers, but I wasn't getting the results I expected/wanted, so I decomposed it into 1 simple alert to no avail.

PROBLEM: I provide unrealistic threshold values just to test functionality but I only receive 1 email alert notification after I initially enable the Alert.

 

I decomposed 'Average Xmit-Recv Percent Utilization' to 'Recv Percent Utilization' and set the value to a ridiculous value of 1

The trigger condition must exist for more than 1 minute

The Reset Condition is set to the basic 'Reset when trigger conditions are no longer true'

The Alert is checked every 1 minute

Trigger actions: Send me an email (that contains...)

     Interface Full Name

     InPercentUtil

     AlertTriggerTime

     AlertTriggerCount {This inserted just to test if consecutive alerts triggered}

 

I'm expecting to receive a continuous flow of email traffic, but I'm not - why not?Your advice, suggestions, comments, shared misery is welcome!

Theories:

1. The utilization value reported is a snapshot in time and not a calculated valued based over a period of time

2. There is a relationship to the polling interval that I'm not considering


Viewing all articles
Browse latest Browse all 20396

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>