Creating an Anomaly Alert
An anomaly alert is only useful if you have configured Anomaly Detection to monitor a stream of data. Installation of ThingWorx Analytics is required in order to use anomaly alerts. For more information about setting up Anomaly Detection, see Implementing Anomaly Detection.
1. In ThingWorx Composer, open the Thing Shape, Thing Template, or Thing for which you want to create an alert.
2. From the drop-down field at the top of the page, select Properties and Alerts.
3. To start creating a new alert, do one of the following:
In the My Properties table, click
in the Alerts column of the property for which you want to add an alert.
Click Alerts to open the Alerts page and click Add.
The New Alert side panel opens.
4. In the side panel provide the following information to define the new alert:
When checked, the alert is active.
User-defined name to identify the alert.
User-defined description of the alert.
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.
The priority of the new alert, relative to existing alerts.
5. Click
to save the alert parameters and close the panel.
6. Click Save.
If you created the anomaly alert on a Thing property, a new ThingWatcher instance is initialized and can begin receiving data to prepare for anomaly detection. If you created the anomaly alert on a Thing Template or a Thing Shape, it will not be initialized but will be available for future use.
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.
Was this helpful?