Anomaly Detection

Overview Copied

Anomaly Detection rules are calculated using historical data. This data is used to generate a dataset and run a rule against. Based on the data you can determine what normality looks like which allows you to create rules to raise alerts when an anomaly is detected.

Geneos requires at least a day of data to be able to perform anomaly detection.

When creating the Anomaly Detection rules in Geneos, you use Data Sets (Time series) in their calculations. Time series allow these rules to be adaptive based on prior knowledge of the daily or weekly variations in the data the time series is applied to.

Time series model data that is read by the Gateway from a user-defined database or from the Gateway Hub. These models can then be used as part of the Anomaly Detection functionality.

In the Gateway, Anomaly Detection rules are evaluated against time series. The time series is loaded from either:

User defined database — time series is loaded when the Gateway starts and is periodically refreshed. For more information, see Database driven Time Series in Data Sets (Time Series).
Gateway Hub — a predefined algorithm runs on the data stored in Gateway Hub, and generates a dataset that can be used in the Gateway. It is a statistical algorithm that returns a set of statistical measures. For more information, see Gateway Hub driven Time series in Data Sets (Time Series).

For more information on how to create Time Series, see Create a Time Series in Time Series.

Set up Anomaly Detection Copied

If you are not using Gateway Hub, you need to set up the time series database. For more information, see Database driven Time Series in Data Sets (Time Series).

If you are using Gateway Hub as a source of your data:

Ensure that Gateway is connected to a Gateway Hub. For more information, see Connecting to Gateway Hub. In production environments, you should connect to Gateway Hub securely:
- (Optional) If the Gateway Hub is configured to use SSO, you will need to start Gateway securely. For more information, see Connecting using SSO.
Create data sets and time series in Gateway. For more information, see Create a Time Series in Data Sets (Time Series).
Create rules in Gateway that use your time series data. For more information, see Rules, Actions, and Alerts.

At this point, your Anomaly Detection rules are configured. Once sufficient data has been logged, the gate way starts receiving alerts based on the setup.

You can also configure the Gateway Hub data plug-in to see the status of Gateway publishing to Gateway Hub. For more information, see Gateway Plug-Ins.

Examples Copied

Examples of using Anomaly Detection include:

A moving threshold during the day to deal with spikes of traffic at known intervals.
Ensuring that a value stays within a safe zone during the day.

Below, you can find examples of how to define rules depending on whether your data sets are database driven or loaded from Gateway Hub.

Rules based on data sets loaded from Gateway Hub Copied

The example below shows a rule referring to a max aggregation of a time series defined as demo5. According to the rule logic, if the value of the rule target goes above the value of the time series at that point in time, then the severity is set to critical.


if value > timeseries "demo5.max" then severity critical
else severity ok
endif

The example below shows a rule referring to a stdev aggregation of a time series defined as demo5. According to the rule logic, if the value of the rule target goes above the value of the time series at that point in time, then the severity is set to critical.


if value > timeseries "demo.stdev" then severity critical
else severity ok
endif

For more information on available statistical time series aggregations used in rules, see Type — Hub in Data Sets (Time Series).

Rules based on data sets loaded from the database Copied

The example below shows a rule referring to a time series defined as maxCpu. According to the rule logic, if the value of the rule target goes above the value of the time series at that point in time, then the severity is set to critical.


if value > timeseries "maxCPU" then  severity critical
else  severity ok
endif

A time series is typically created using historical data pertaining to certain managed variables. In the above example, the time series maxCpu might have been created using historical data gathered on the rule target itself. Hence in effect the rule is comparing the current behaviour of the value to its historical behaviour.

A rule can typically refer to multiple time series.


if value > timeseries "cpuUpperLimit" or value < timeseries "cpuLowerLimit" then  severity critical
else if value > timeseries "cpuUpperWarn" or value < timeseries "cpuLowerWarn" then  severity warning
else  severity ok
endif

In the above example high and low thresholds for both warning and critical severity have been defined as time series. Typically such time series would have been generated by running different functions on the same historical data.

See Create a Time Series in Data Sets (Time Series) for more information.

Troubleshooting Copied

Problem accessing the data set Copied

If your Gateway does not have access to the data set generated by Gateway Hub, check the Gateway and Gateway Hub connectivity and any errors. This includes errors with Gateway unable to get SSO tokens from Gateway Hub. See SSO OpenAPI for more information.

Alerts are not generated Copied

Historical data must exist for the alerts to be generated based on this data. As long as the data you are summarising in the data set has sufficient history to cover the data period selected in the setup, alerts will be generated.

Make sure you have enough historical data for the alerts to be generated.