 |
VOOZH | about |
|
VOOZH | about |
Datadog offers multiple configuration options for the Azure integration. This guide provides an overview of the various options available for getting started with Azure, with links to Azure resources and tutorials that address specific use cases.
If you haven’t already, create a Datadog account.
Follow the instructions on this page to set up the Azure integration through an app registration, available for all Datadog sites.
Datadog’s Azure integration is built to collect all metrics from Azure Monitor. The Integrations page shows a curated list of predefined sub-integrations that provide additional out-of-the-box dashboards and monitors for specific Azure services. Many of these integrations are installed by default when Datadog recognizes data coming in from your Azure account. However, Datadog can ingest metrics from any Azure Monitor-supported resource, even if it doesn’t have a dedicated sub-integration tile.
You can find your Azure metrics in the metrics summary page in the Datadog platform by navigating to Metrics > Summary and searching for Azure.
Use tag filters to control which Azure resources have their metrics collected by Datadog. Configure tag filters in the Configuration tab of the Azure integration tile. A tag filter is a comma-separated list of tags in the form key:value. Only resources that match at least one tag in the filter have their metrics collected.
You can use wildcards in your tag filters:
? matches a single character.* matches multiple characters.To exclude resources with a given tag, prefix the tag with !. Exclusion takes precedence over inclusion. A resource matches the filter if it matches any tag in the list.
For example: datadog:monitored,env:production,!plan_tier:basic,instance-type:c1.*
This filter collects metrics from resources tagged with datadog:monitored or env:production, excludes resources tagged with plan_tier:basic, and includes resources with an instance-type tag matching c1.*.
If no tag filter is set, Datadog collects metrics from all Azure resources.
You can use the automated log forwarding feature to setup and configure the services and diagnostic settings needed to forward logs to Datadog. If an automated log forwarding control plane already exists in the tenant, this flow modifies it and extends its scope to include the selected subscriptions or management groups. For more detail, see Azure Automated Log Forwarding Setup.
Datadog recommends using the Agent or DaemonSet to send logs from Azure. If direct streaming isn’t possible, use the Configure Log Forwarding flow in the Azure integration to set up and manage automated log forwarding directly in Datadog. You can also deploy log forwarding with an Azure Resource Manager (ARM) template. Both methods automatically manage and scale log forwarding services.
Archiving logs to Azure Blob Storage requires an App Registration. If you haven’t already, follow the automatic or manual setup instructions to configure the integration using an App Registration. App Registrations created for archiving purposes do not need the Monitoring Reader role.
After configuring an App Registration, create a log archive that writes to Azure Blob Storage.
Note: If your storage bucket is in a subscription being monitored through the Azure Native integration, a redundancy warning appears in the Azure integration tile. This warning can be safely ignored for log archiving.
Use tag filters to control which Azure resources have their logs forwarded to Datadog. To configure tag filters for logs, click Configure Log Forwarding in the Azure integration tile and follow the flow. A tag filter is a comma-separated list of tags in the form key:value. Only resources that match at least one tag in the filter have their logs forwarded.
You can use wildcards in your tag filters:
? matches a single character.* matches multiple characters.To exclude resources with a given tag, prefix the tag with !. Exclusion takes precedence over inclusion. A resource matches the filter if it matches any tag in the list.
For example: datadog:monitored,env:production,!plan_tier:basic,instance-type:c1.*
This filter forwards logs from resources tagged with datadog:monitored or env:production, excludes resources tagged with plan_tier:basic, and includes resources with an instance-type tag matching c1.*.
If no tag filter is set, Datadog forwards logs from all Azure resources.
After you set up your Azure integration, Datadog crawlers automatically collect Azure metrics, but you can gain even deeper visibility into your Azure instances with the Datadog Agent. Installing the Datadog Agent into your environment allows you to collect additional data including, but not limited to:
You can also use the built-in StatsD client to send custom metrics from your applications, to correlate what’s happening with your applications, users, and system. See the guide on Why should I install the Datadog Agent on my cloud instances? for more information on the benefits of installing the Datadog Agent on your instances.
Use the Azure extension to install the Datadog Agent on Windows VMs, Linux x64 VMs, and Linux ARM-based VMs. You can also use the AKS Cluster Extension to deploy the Agent to your AKS Clusters.
To install the Agent based on operating system or CI and CD tool, see the Datadog Agent installation instructions.
Note: Domain controllers are not supported when installing the Datadog Agent with the Azure extension.
The Datadog AKS Cluster Extension allows you to deploy the Datadog Agent natively within Azure AKS, avoiding the complexity of third-party management tools. To install the Datadog Agent with the AKS Cluster Extension:
See Troubleshooting in the Azure Advanced Configuration guide.
Still need help? Contact Datadog support.
Additional helpful documentation, links, and articles:
| |
