You use this app to view and process the anomalies that the system has detected based on the configured anomaly detection rules.
For more information, see View and Process Anomalies App.
For more information about anomaly detection in general, see Anomaly Detection.
Date and time when the data first showed this anomaly.
Date and time when the data last showed this anomaly.
Number of days that the measurement data has shown the anomaly described by the anomaly detection rule.
For more information, see Anomaly Duration in the Energy Data Services API Guide.
Number of times the anomaly has been detected by the system. With each new detection run, this number is updated until the anomaly is no longer detected.
Shows the status of the anomaly.
| Anomaly Status | Description |
|---|---|
| Active |
The anomaly is currently being detected. See the Anomaly Start Date and Anomaly Start Time columns for the date and time when the anomaly started and the Anomaly Duration column for the number of days that the data has shown this anomaly. You can set active anomalies to Suppressed if you don't want to actively monitor them. |
| Ended |
The anomaly is no longer being detected. See the Anomaly End Date and Anomaly End Time columns for the date and time when the anomaly was detected for the last time and the Anomaly Duration column for the number of days that the data has shown this anomaly. This is a final status that cannot be manually changed. |
| Suppressed |
The anomaly is currently still being detected and was manually set to Suppressed. You can set active anomalies to Suppressed if you don't want to actively monitor them, either in this app or using the Anomaly Support API. You can filter the list of detected anomalies using the Anomaly Status filter. You can manually change the status from Suppressed back to Active as long as the anomaly is still being detected by the system. When the system no longer detects this anomaly, it is automatically assigned the status Ended. |
| Closed |
The anomaly is no longer being detected. You can set active anomalies to Closed when you know the event causing the anomaly has ended or the problem has been solved. You can set this status for selected anomalies either in this app or using the Anomaly Support API. This is a final status that cannot be changed. |
Depending on what has been configured for the anomaly detection rule, you can see in this section whether a notification has been sent for the anomaly and what the state of the notification processing is.
The number of days that have passed since the start of the anomaly before the notification is created and sent to the configured destination.
This number of days has been configured for the anomaly detection rule in the Configure Anomaly Detection Rules app.
The notification can have one of the following states, which have a date and time attached:
When the notification is created after the number of Days Before Notification have passed, the notification state is New.
When the system processes the notification, the notification state is Sending in Progress.
If the system could send the notification to the destination successfully, the notification state is Sent.
If the system could not send the notification to the destination after several attempts, the notification state is Sending Failed.
Make sure that the notification configuration is correct and check the settings in the Configure Anomaly Notifications app.
If the anomaly is no longer active and has the anomaly status Ended or Suppressed when the system processes the notification, no notification is sent and the notification state is Obsolete.
Access the product documentation and additional resources for SAP Cloud for Energy on the SAP Help Portal.