Parameter | Description | |
---|---|---|
Enabled | When checked, the alert is active. | |
Name | User-defined name to identify the alert. | |
Description | User-defined description of the alert. | |
Property | The property to which the alert will be applied. An anomaly alert can only be applied to properties of NUMBER, INTEGER, or LONG data types. | |
Alert Type | Select Anomaly and provide the subsequent information: | |
Outbound Anomaly Rate | The rate at which anomalies will be reported. Data is buffered for this amount of time (for example, 3 seconds). When averaged, if there is an anomalous value for more than 50% of that time, an anomaly is reported. | |
Min. Data Collection | The minimum amount of time required for data collection before the anomaly model can be built. | |
Certainty % | A tunable threshold that defines how much certainty there must be before a set of values can be considered anomalous. Acceptable values must be greater than 50 and less than 100. | |
Priority | The priority of the new alert, relative to existing alerts. |
If the new anomaly alert on a Thing property is not created successfully, a value of Initialization Failed appears in the Status column on the Alerts page. This failure can occur if the external Training or Results services are not properly installed and running, or when the services are not defined in the AlertProcessingSubsystem Configuration. To identify the specific error, see the Application Log. |