Anomaly Detection allows you to create custom alerts, set up customized alerts, and transform metric events configuration. You can also save time and create a custom alert in Notebooks while using the app.
Prerequisites
To use the latest version of Anomaly Detection, you need to have appropriate permissions. For more information, see Anomaly Detection overview.
Create or edit an advanced custom alert
To manually create or edit an advanced custom alert configuration, you can use Anomaly Detection or Settings. Because Anomaly Detection is deprecated, we recommend using Settings instead.
Go to Anomaly Detection.
Select New alert > Create your own custom alert to create a new alert. To edit an existing custom alert, select any custom alert from the list.
In Data type, choose Timeseries to trigger alerts based on timeseries-based thresholds and pattern deviation, or choose Records to trigger alerts based on matching record as a potential anomaly or event worth reporting. To learn about the difference between the two, see Data types.
In Query, provide the DQL query to fetch your data.
We recommend that you use the interval: 1m parameter to ensure proper data resolution for the analysis.
Optional In Delay, set the timeframe between query executions. You can choose between Minutes or Seconds.
The default and minimum time is 1 Minute. You can set the Delay parameter up to 60 Minutes, or its equivalent in seconds.
Set Actor to a service user or regular user.
By default, after editing the custom alert's configuration, the actor changes to the user who updated it. You will get a warning message confirming whether you want to overwrite the existing configuration or make a copy of the custom alert with your changes.
If the custom alert was created with a service user and you have permission to use the service user, you can update the configuration without overwriting the service user actor; otherwise, you'll get a warning about restricted service user access.
Choosing the alert identity field allows you to exclude fields with dynamic values from alerting. This means that only the fields provided in Alert identity fields will be used to create and update the events. Other fields will not be alerted on, but will still appear as a reference field.
Optional In Delay, set the time between query executions. You can choose between Minutes or Seconds.
The default and minimum time is 1 Minute. You can set the Delay parameter up to 60 Minutes, or its equivalent in seconds.
Set Actor to a service user or regular user.
By default, after editing the custom alert's configuration, the actor changes to the user who updated it. You will get a warning message confirming whether you want to overwrite the existing configuration or make a copy of the custom alert with your changes.
If the custom alert was created with a service user and you have permission to use the service user, you can update the configuration without overwriting the service user actor; otherwise, you'll get a warning about restricted service user access.
Optional To see a demonstration of your alert condition, select Preview.
Expand Add details.
In General information, set a Title and Description for your custom alert. You can use Markdown in your custom alert description.
In Create event template, configure the event triggered by the configuration. For details, see Event template.
Select Create to create a simple custom alert or select Save to update your configuration.
Go to Settings > Analyze and alert > Alerts > All alerts.
Select Custom alerts.
Select New alert > Create your own custom alert to create a new alert. To edit an existing custom alert, select any custom alert from the list.
In Data type, choose Timeseries to trigger alerts based on timeseries-based thresholds and pattern deviation, or choose Records to trigger alerts based on matching record as a potential anomaly or event worth reporting. To learn about the difference between the two, see Data types.
In Query, provide the DQL query to fetch your data.
We recommend that you use the interval: 1m parameter to ensure proper data resolution for the analysis.
Optional In Delay, set the timeframe between query executions. You can choose between Minutes or Seconds.
The default and minimum time is 1 Minute. You can set the Delay parameter up to 60 Minutes, or its equivalent in seconds.
Set Actor to a service user or regular user.
By default, after editing the custom alert's configuration, the actor changes to the user who updated it. You will get a warning message confirming whether you want to overwrite the existing configuration or make a copy of the custom alert with your changes.
If the custom alert was created with a service user and you have permission to use the service user, you can update the configuration without overwriting the service user actor; otherwise, you'll get a warning about restricted service user access.
Choosing the alert identity field allows you to exclude fields with dynamic values from alerting. This means that only the fields provided in Alert identity fields will be used to create and update the events. Other fields will not be alerted on, but will still appear as a reference field.
Optional In Delay, set the time between query executions. You can choose between Minutes or Seconds.
The default and minimum time is 1 Minute. You can set the Delay parameter up to 60 Minutes, or its equivalent in seconds.
Set Actor to a service user or regular user.
By default, after editing the custom alert's configuration, the actor changes to the user who updated it. You will get a warning message confirming whether you want to overwrite the existing configuration or make a copy of the custom alert with your changes.
If the custom alert was created with a service user and you have permission to use the service user, you can update the configuration without overwriting the service user actor; otherwise, you'll get a warning about restricted service user access.
Optional To see a demonstration of your alert condition, select Preview.
Expand Add details.
In General information, set a Title and Description for your custom alert. You can use Markdown in your custom alert description.
In Create event template, configure the event triggered by the configuration. For details, see Event template.
Select Create to create a simple custom alert or select Save to update your configuration.
Whenever you Create or Save your custom alert, its configuration gets automatically validated. If the there's no errors present in your configuration, you'll be able to save or update your configuration. If there are any errors, the section will be highlighted with red and marked with Error message under the section title.
Check the Status of the new configuration shortly after creation to ensure there are no errors in the execution.
Create an advanced custom alert in Notebooks
With Dynatrace Intelligence for Notebooks, you can preview your custom alert configuration and evaluate its effectiveness. This option takes you to Notebooks, where you configure the query and monitoring strategy, and then back to Anomaly Detection to create an event template.
Go to Anomaly Detection.
Select New alert > Open a custom alert in Notebooks.
Select a notebook in which you want to preview your configuration.
This action takes you to Notebooks.
Add a new DQL or Metrics section and query the data you're interested in.
For a DQL query, we recommend that you use the interval: 1m parameter to ensure proper data resolution for the analysis.
Optional Select , then select one or multiple segments you want to filter by.
Anomaly Detection allows you to create custom alerts, set up customized alerts, and transform metric events configuration. You can also save time and create a custom alert in 
Notebooks while using the app.
Settings. Because