...
Whilst each of the fields are explained below in more detail, please click here to jump to a table that provides a some example configurations and (e.g. I want to check a days behaviour with the behaviour on the same days over the last 2 weeks).
Field | Default | Description | ||
---|---|---|---|---|
Period to Monitor | Month | This represents the period of time you want to compare to. Combined with the offset that can be defined, this will determine what the latest data will be compared to. Choose from:
| ||
Interval to Monitor | Month | This represents the interval within that period that you wish to monitor. The options available in the dropdown will depend on the Period to Monitor that has been chosen. Period: Year
Period: Month
Period: Week
Period: Day
| ||
Source Profile From | Data Prior to Check Period | Choose from:
| ||
Data Prior to Check Period is chosen... compare recent data against the period of time directly prior to the period being checked. | ||||
Offset (<period selected>) | 1 | Specifying a number greater than one here specifies an offset as to how many prior periods should be skipped when determining the period of time to compare the recent behaviour against. By default this would be "1" and this means:
Some examples where the offset may be changed to something other than "1":
| ||
<period selected> to Average | 1 | This will define the number of prior periods of time that will be used to derive an average profile which the recent data can then be compared to to determine if it is suspect or not. For example if the period selected is:
| ||
Data Ending on a Fixed Date is chosen... compare recent data against the period of time directly prior to the end date that has been specified. | ||||
Fixed Date | Current Date | Amend the Fixed date using the arrows or the calendar | ||
<period selected> to Average | 1 | As above - it will average the period directly prior to the period ending that has been specified. | ||
Thresholds | ||||
High Threshold | 20 | Use the tickbox to the left of the High Threshold label to enable/disable the high threshold check. The value entered here is effectively the sensitivity of the upper limit that is permitted when the recent data is compared against the historical data (i.e. where the data spikes). This should be considered in conjunction with the type of threshold listed below. | ||
Low Threshold | 30 | Use the tickbox to the left of the Low Threshold label to enable/disable the low threshold check. The value entered here is effectively the sensitivity of the lower limit that is permitted when the recent data is compared against the historical data (i.e. where the data drops). This should be considered in conjunction with the type of threshold listed below. | ||
Threshold Type | Percent | Choose from:
| ||
Raise a notification after X consecutive breaches | 1 | This setting allows you to control how sensitive the check is and whether it should only alert you if the issue is a consistent problem. For example, you maybe performing a daily check against the same day last week. You might only want it to tell you if a problem is found 2 days in a row, in this case this would be set to "2". |
Click OK to save the Monitoring Strategy.
Info |
---|
Once the Strategy has been set up, Sigma will review the data each night and create any relevant notifications in the Notifications tab |
Anchor | ||||
---|---|---|---|---|
|
...