...
The Dynamic Baseline and Threshold Tool includes various configuration options so that you can tune the algorithm to learn differently depending on the metric being used. The tool comes with several metrics already configured. It is a requirement of the system that the stats modelling is completed for the metric you require to be baseline, this is how the NMIS API extracts statistical information from the performance database.
...
| Configuration Option | Description | Example |
|---|---|---|
| active | Is baselining this metric active or not, values are true or false | true |
| metric | Which NMIS datapoint data point or variable, equates to an RRD DS | RouteNumber |
| type | Which NMIS model section or metric | RouteNumber |
| section | What is the section name in the node info, just run it, otherwise the section must exist. | |
| nodeModel | This is a regex which defines which NMIS models should be matched | CiscoRouter |
| event | The name of the event to use, will default to Proactive Baseline type metric if none provided. | Proactive Route Number Change |
| indexed | Is this variable indexed or not | false |
| threshold_exceeds | Ignored if undef otherwise the value must ALSO exceed this threshold to raise an event | undef |
| threshold_period | How many minutes should the value to be baselined be averaged, e.g. -5 minutes is the last poll, -15 minutes would be the average of the last 15 minutes, -1 hour would be the last 60 minutes. | -5 minutes |
| multiplier | How many standard deviations to vary the baseline by. | 1 |
| weeks | The number of weeks to look back | 0 |
| hours | The number of hours to include in the baseline metrics | 8 |
...