Still a work in progress...
What is this functionality and why would anyone what it? What dives operators to this page?
Table of Contents |
---|
Consider a certain situation that our operator would like to be aware of in the event that it occurred. Certainly there are many situations we would like to be aware of before our boss (or customer) tells us about itbefore customers begin complaining. It is with these situations in mind we should consider provisioning thresholding in NMIS.
Thresholding
Thresholding can be accomplished with the following steps:
- What data is being collected which can be thresholded?
- Add a threshold property to the model section.
- Add threshold values to the Common-threshold.nmis file.
- Add statistics extraction (pulling data from the RRD file and formating it) to the Common-stats.nmis file.
- Test the newly provisioned thresholding policy.
- Consider advanced threshold using controls (Adding boolean logic and regular expressions for precision selection).
Consider the following questions:
- What would you like to threshold?
- How feasible is the thresholding candidate?
- Can the metrics be reduced/translated/combined into a meaningful threshold?
- What should the corresponding event name for the threshold be?
- The event name must include "Proactive" at the beginning in order for NMIS to process it correctly. e.g. "Proactive Temp" or Proactive CPU Load".
Steps and Examples
#1. Add a threshold property to the model section.
#2. Add threshold values to Common-threshold.nmis
#3. Add statistics extraction to Common-stats.nmis
Thresholds used to drive event reporting can be created based on any measurable attribute. In this example we'll cover something in the systemHealth section.
...