Azure Alerts is a unified notification hub for all types of important conditions found in Azure monitoring data.
The integration of Azure Alerts enables you to consume alerts, which are automatically transformed into events that are leveraged by Davis AI for deeper insights.
How it works
Azure Alerts are consumed via webhooks that are configured in your Azure Alert Rules.
The alerts are mapped to the closed matching known entity. This means that they either map to their related Azure resource entity or, as a fallback, to the Azure subscription of the resource.
The following alert types are supported:
Metric alerts are complementary to Dynatrace integration of Azure Monitor metrics.
Metric alerts allow you to retrieve metric based events without the need to push the metrics to Dynatrace. This is helpful in reducing API and network pressure, especially in cases where you might not need the metric (for example, for charting purposes).
The event type is defined based on alert severity:
Activity Alerts provide various types of notifications including Administrative, Service Health, and Resource Health.
This opens up a whole new set of insights that you can add to your performance telemetry, including a maintenance event that signifies temporary unavailability.
- Enabled Azure Monitor integration
- A Dynatrace API-token with access scope
Data ingest, e.g.: metrics and events
- One or more designated ActiveGates with valid TLS certificate
Create an API token
To generate an API token:
- Select Settings in the navigation menu.
- Go to Integration > Dynatrace API.
- Click Generate token.
- Enter a name for your token.
- Select the Data ingest, e.g.: metrics and events permission.
- Click Generate.
You can assign multiple permissions to a single token, or you can generate several tokens, each with different access levels, and use them accordingly. Check your organization's security policies for best practices.
Set up an ActiveGate to consume Azure Alerts
The Azure Alert webhooks require a valid TLS certificate (No self-signed certificate) to communicate via HTTPS. For details, see how-To configure custom SSL certificate for an ActiveGate.
Add the following lines to your ActiveGate
custom.propertiesfile and restart the ActiveGate after the configuration has been applied:
[azure_monitoring] event_servlet = true
Note The ActiveGate designated to consume Azure Alerts doesn't necessary have to be the same ActiveGate that runs the Azure Monitor integration.
Set up Azure Alert Rules
Read more about Azure Alert Rules configuration.
When defining action rules, use following settings:
Enable the common alert schema
Provide ActiveGate access for Azure Alert source IP addresses
You can find the most recent list of source IP addresses in the Azure documentation.
ActiveGate isn't reachable
If your ActiveGate isn't reachable while sending an alert, Azure Alerts will re-attempt the send.
If an event is sent in an unknown format (for example, common schema) or sent from a subscription that is unknown to Dynatrace (for example, the provided service principal doesn't have read permissions to the subscription), the event will be dropped. In the Azure Integration config section in the settings, you can view statistics of the events which couldn't be handled.