Difference between revisions of "UM:Data Collection"

Jump to navigation Jump to search
14 bytes removed ,  22:43, 7 May 2012
Line 147: Line 147:
'''Figure 5: Threshold processing algorithm'''
'''Figure 5: Threshold processing algorithm'''


<center>[[Image:]]</center>
[[File:Threshold_processing_alg.png||none|alt=Threshold processing algorithm|Threshold processing algorithm]]


As you can see from this flowchart, threshold order is very important. Let's consider the following example: you have DCI representing CPU utilization on the node, and you wish two different events to be generated – one when CPU utilization exceeds 50%, and another one when it exceeds 90%. What happens when you place threshold “> 50” first, and “> 90” second? Table 4 shows values received from host and actions taken by monitoring system (assuming that all thresholds initially unarmed):
 
As you can see from this flowchart, threshold order is very important. Let's consider the following example: you have DCI representing CPU utilization on the node, and you wish two different events to be generated - one when CPU utilization exceeds 50%, and another one when it exceeds 90%. What happens when you place threshold "> 50" first, and "> 90" second? Table 4 shows values received from host and actions taken by monitoring system (assuming that all thresholds initially unarmed):


'''Table 4: Actions taken by monitoring system'''
'''Table 4: Actions taken by monitoring system'''
Line 164: Line 165:
|-
|-
| 55
| 55
| When checking first threshold (“> 50”), the system will find that it's not active, but condition evaluates to true. So, the system will set threshold state to “active” and generate event associated with it.
| When checking first threshold ("> 50"), the system will find that it's not active, but condition evaluates to true. So, the system will set threshold state to "active" and generate event associated with it.


|-
|-
| 70
| 70
| When checking first threshold (“> 50”), the system will find that it's already active, and condition evaluates to true. So, the system will stop threshold checking and will not take any actions.
| When checking first threshold ("> 50"), the system will find that it's already active, and condition evaluates to true. So, the system will stop threshold checking and will not take any actions.


|-
|-
| 95
| 95
| When checking first threshold (“> 50”), the system will find that it's already active, and condition evaluates to true. So, the system will stop threshold checking and will not take any actions.
| When checking first threshold ("> 50"), the system will find that it's already active, and condition evaluates to true. So, the system will stop threshold checking and will not take any actions.


|}
|}
Please note that second threshold actually is not working, because it's “masked” by the first threshold. To achieve desired results, you should place threshold “> 90” first, and threshold “> 50” second.
Please note that second threshold actually is not working, because it's "masked" by the first threshold. To achieve desired results, you should place threshold "> 90" first, and threshold "> 50" second.


You can disable threshold ordering by checking '''Always process all thresholds''' checkbox. If it is marked, system will always process all thresholds.
You can disable threshold ordering by checking '''Always process all thresholds''' checkbox. If it is marked, system will always process all thresholds.


==== Threshold Configuration ====
==== Threshold Configuration ====
AutoPatrol
191

edits

Navigation menu