Network Performance Monitoring is now generally available! Network Monitoring is now available!

Microsoft Azure

Crawler Crawler

Overview

Connect to Microsoft Azure to:

  • Get metrics from Azure VMs with or without installing the Agent.
  • Tag your Azure VMs with Azure-specific information (e.g. location).
  • Get metrics for other services: Application Gateway, App Service (Web & Mobile), Batch Service, Event Hub, IOT Hub, Logic App, Redis Cache, Server Farm (App Service Plan), SQL Database, SQL Elastic Pool, Virtual Machine Scale Set, and many more.

Related integrations include:

IntegrationDescription
Analysis ServicesA service that provides data models in the cloud.
API ManagementA service to publish, secure, transform, maintain, and monitor APIs.
App ServiceA service for deploying and scaling web, mobile, API and business logic applications
App Service EnvironmentA service that provides an environment for securely running App Service apps at high scale.
App Service PlanA set of compute resources for a web app to run.
Application GatewayA web traffic load balancer that enables you to manage traffic to your web applications.
AutomationA service that provides automation and configuration management across your environments.
Batch ServiceManaged task scheduler and processor
Cognitive ServicesAPIs, SDKs, and services available to help build applications without AI or data science knowledge.
Container InstancesA service to deploy containers without the need to provision or manage the underlying infrastructure.
Container ServiceA production-ready Kubernetes, DC/OS, or Docker Swarm cluster.
Cosmos DBA database service that supports document, key-value, wide-column, and graph databases.
Customer InsightsEnables organizations to bring together data sets to build a 360° view of their customers.
Data FactoryA service to compose data storage, movement, and processing services into automated data pipelines.
Data Lake AnalyticsAn analytics job service that simplifies big data.
Data Lake StoreA no limits data lake that powers big data analytics.
Database for MariaDBA service that provides fully managed, enterprise-ready community MariaDB database.
Event GridAn event routing service that allows for uniform event consumption using a publish-subscribe model.
Event HubLarge scale data stream managed service
ExpressRouteA service to extend your on-premises networks into the cloud.
FirewallCloud-native network security to protect your Azure Virtual Network resources.
HDInsightsA cloud service that processes massive amounts of data.
IOT HubConnect, monitor, and manage billions of IOT assets
Key VaultA service to safeguard and manage cryptographic keys and secrets used by cloud applications and services.
Load BalancerScale your applications and create high availability for your services
Logic AppBuild powerful integration solutions
Network InterfacesEnables VM communication with internet, Azure, and on-premises resources.
Notification HubsA push engine that allows you to send notifications to any platform from any backend.
Public IP AddressA resource that enables inbound communication and outbound connectivity from the Internet.
Redis CacheManaged data cache
RelaySecurely expose services that run in your corporate network to the public cloud.
SearchA search-as-a-service cloud solution that provides tools for adding a rich search experience.
StorageStorage for blobs, files, queues, and tables
Stream AnalyticsAn event-processing engine to examine high volumes of data streaming from devices.
SQL DatabaseHighly scalable relational database in the cloud
SQL Database Elastic PoolManage the performance of multiple databases
Virtual MachineVirtual machine management service
Virtual Machine Scale SetDeploy, manage, and autoscale a set of identical VMs

Setup

Installation

Integrate your Microsoft Azure account with Datadog using the Azure CLI tool or the Azure portal. This integration method works automatically for all Azure Clouds: Public, China, German, and Government. Follow the instructions below and Datadog detects automatically which Cloud you are using to complete the integration.

Integrating through the Azure CLI

To integrate Datadog with Azure using the Azure CLI, you must have Azure CLI installed.

First, log in to the Azure account you want to integrate with Datadog:

az login

Run the account show command:

az account show

Enter the generated Tenant ID value in the Datadog Azure Integration tile under Tenant name/ID.

Create an application as a service principal using the format:

az ad sp create-for-rbac --role reader --scopes /subscriptions/{subscription_id}
  • This command grants the Service Principal the reader role for the subscription you would like to monitor.
  • The appID generated from this command must be entered in the Datadog Azure Integration tile under Client ID.
  • Add --name <CUSTOM_NAME> to use a hand-picked name, otherwise Azure generates a unique one. The name is not used in the setup process.
  • Add --password <CUSTOM_PASSWORD> to use a hand-picked password. Otherwise Azure generates a unique one. This password must be entered in the Datadog Azure Integration tile under Client Secret.

First, log in to the Azure account you want to integrate with Datadog:

azure login

Run the account show command:

az account show

Enter the generated Tenant ID value in the Datadog Azure Integration tile under Tenant name/ID.

Create a name and password:

azure ad sp create -n <NAME> -p <PASSWORD>
  • The <NAME> is NOT used but is required as part of the setup process.
  • The <PASSWORD> you choose must be entered in the Datadog Azure Integration tile under Client Secret.
  • The Object Id returned from this command is used in place of <OBJECT_ID> in the next command.

Create an application as a service principal using the format:

azure role assignment create --objectId <OBJECT_ID> -o Reader -c /subscriptions/<SUBSCRIPTION_ID>/
  • This command grants the Service Principal the reader role for the subscription you would like to monitor.
  • The Service Principal Name generated from this command must be entered in the Datadog Azure Integration tile under Client ID.
  • <SUBSCRIPTION_ID> is the Azure subscription you would like to monitor, and is listed as ID with azure account show or in the portal.

First, log in to the Azure account you want to integrate with Datadog:

azure login

Run the account show command:

az account show

Enter the generated Tenant ID value in the Datadog Azure Integration tile under Tenant name/ID.

Create a name, home-page, identifier-uris, and password:

azure ad app create --name "<NAME>" --home-page "<URL>" --identifier-uris "<URL>" --password "<PASSWORD>"
  • The name, home-page, and identifier-uris are NOT used but are required as part of the setup process.
  • The password you choose must be entered in the Datadog Azure Integration tile under Client Secret.
  • The AppId returned from this command is used in the next command and must be entered in the Datadog Azure Integration tile under Client ID.

Create a Service Principal using:

Azure cli <0.10.2:

azure ad sp create {app-id}

Azure cli >= 0.10.2:

azure ad sp create -a {app-id}
  • The Object Id returned from this command is used in place of <OBJECT_ID> in the next command.

Create an Active Directory application using the format:

azure role assignment create --objectId <OBJECT_ID> --roleName Reader --subscription <SUBSCRIPTION_ID>
  • This command grants the Service Principal the reader role for the subscription you would like to monitor.
  • <SUBSCRIPTION_ID> is the Azure subscription you would like to monitor, and is listed as ID with azure account show or in the portal.

Integrating through the Azure portal

  1. Create a web application in your Active Directory and pass the correct credentials to Datadog.
  2. Give this application read-access to any subscriptions you would like to monitor.
Creating the Web Application
  1. Under Azure Active Directory, navigate to App Registrations and click New registration:

  2. Enter the following and click the Create button. Note: The name and sign-on URL are not used but required for the setup process.

    • Name: Datadog Auth
    • Supported Account Types: Accounts in this organizational directory only (Datadog)
    • Redirect URI - optional - https://app.datadoghq.com
Giving Read Permissions to the Application
  1. Navigate to Subscriptions through the search box or the left sidebar:

  2. Click on the subscription you would like to monitor.

  3. Select Access control (IAM) in the subscription menu then Add -> Add role assignment:

  4. For Role, select Reader. Under Select, choose the name of the Application you just created:

  5. Click Save.

  6. Repeat this process for any additional subscriptions you want to monitor with Datadog. Note: Users of Azure Lighthouse can add subscriptions from customer tenants.

Note: Diagnostics must be enabled for ARM deployed VMs to collect metrics, see Enable diagnostics.

Completing the Integration
  1. Under App Registrations, select the App you created, copy the Application ID and Tenant ID, and paste the values in the Datadog Azure Integration tile under Client ID and Tenant ID

  2. For the same app, go to Manage -> Certificates and secrets

  3. Add a new Client Secret called datadogClientSecret, select a timeframe for Expires, and click Add:

  4. When the key value is shown, copy and paste the value in the Datadog Azure Integration tile under Client Secret and click Install Integration or Update Configuration.

Configuration

Optionally, you can limit the Azure VMs that are pulled into Datadog by entering tags under Optionally filter to VMs with tag.

This comma separated list of tags in the form <KEY>:<VALUE> defines a filter used while collecting metrics. Wildcards such as ? (for single characters) and * (for multiple characters) can also be used. Only VMs that match one of the defined tags are imported into Datadog. The rest are ignored. VMs matching a given tag can also be excluded by adding ! before the tag. For example:

datadog:monitored,env:production,!env:staging,instance-type:c1.*

Metrics Collection

After the integration tile is set up, metrics are collected by a crawler. To collect additional metrics, deploy the Datadog Agent to your VMs:

Agent installation

  1. In the Azure portal, navigate to your VM -> Settings -> Extensions -> Add and select Datadog Agent.
  2. Click Create, enter your Datadog API key, and click OK.

To install the Agent based on operating system or CICD tool, see the in app Datadog Agent install instructions.

Validation

It may take few minutes for metrics from applications under the new subscription to appear.

Navigate to the Azure VM Default Dashboard to see this dashboard populate with your infrastructure’s data:

Log Collection

To collect logs from all of your Azure services except App Services, follow this general process:

  1. Create an Azure Event Hub from the Azure portal, the Azure CLI, or Powershell.
  2. Setup the Datadog-Azure Function which forwards logs from your event hub to Datadog.
  3. Configure your Azure services to forward their logs to the Event Hub.

Create a new Azure Event Hub function

If you are unfamiliar with Azure functions refer to Create your first function in the Azure portal.

  1. In the Azure portal, navigate to your Function Apps -> Functions and click New function.
  2. Select to build your function In-portal and use the Event Hub trigger template (under More templates…). If needed, install the Microsoft.Azure.WebJobs.Extensions.EventHubs extension.
  3. Enter a Name for your function.
  4. Select or add your Event Hub connection.
  5. Select the Javascript language in the right menu.
  6. Select the Event Hub consumer group and the Event Hub Name to pull logs from.
  7. Click Create.
  8. Create an index.js file and add the Datadog-Azure Function code (replace <DATADOG_API_KEY> with your Datadog API Key).
  9. Save the function.
  10. Under Integrate, set the Event Parameter Name to eventHubMessages and click Save.
  11. Verify your setup is correct by checking the Datadog Log explorer for your logs.

To collect logs from all of your Azure App Services, follow this general process:

  1. Set up Azure Blob Storage from the Azure portal, Azure Storage Explorer, Azure CLI, or Powershell.
  2. Set up the Datadog-Azure Function which forwards logs from your blob storage to Datadog.
  3. Configure your Azure App Services to forward their logs to the Blob Storage.

Create a new Azure Blob Storage function

If you are unfamiliar with Azure functions refer to Create your first function in the Azure portal.

  1. In the Azure portal, navigate to your Function Apps -> Functions and click New function.
  2. Select to build your function In-portal and use the Blob Storage trigger template (under More templates…). If needed, install the Microsoft.Azure.WebJobs.Extensions.Storage extension.
  3. Enter a Name for your function.
  4. Select or add your Storage account connection.
  5. Select the Javascript language in the right menu.
  6. Click Create.
  7. Create an index.js file and add the Datadog-Azure Function code (replace <DATADOG_API_KEY> with your Datadog API Key).
  8. Save the function.
  9. Under Integrate, set the Blob Parameter Name to blobContent and click Save.
  10. Verify your setup is correct by checking the Datadog Log explorer for your logs.

Data Collected

Metrics

azure.cdn_profiles.status.status
(gauge)
Status of Azure CDN Profiles
azure.devices_elasticpools_iothubtenants.c2d.commands.egress.abandon.success
(count)
Number of cloud-to-device commands abandoned by the device
azure.devices_elasticpools_iothubtenants.c2d.commands.egress.complete.success
(count)
Number of cloud-to-device commands completed successfully by the device
azure.devices_elasticpools_iothubtenants.c2d.commands.egress.reject.success
(count)
Number of cloud-to-device commands rejected by the device
azure.devices_elasticpools_iothubtenants.c2d.methods.failure
(count)
The count of all failed direct method calls.
azure.devices_elasticpools_iothubtenants.c2d.methods.request_size
(gauge)
The average min and max of all successful direct method requests.
Shown as byte
azure.devices_elasticpools_iothubtenants.c2d.methods.response_size
(gauge)
The average min and max of all successful direct method responses.
Shown as byte
azure.devices_elasticpools_iothubtenants.c2d.methods.success
(count)
The count of all successful direct method calls.
azure.devices_elasticpools_iothubtenants.c2d.twin.read.failure
(count)
The count of all failed back-end-initiated twin reads.
azure.devices_elasticpools_iothubtenants.c2d.twin.read.size
(gauge)
The average min and max of all successful back-end-initiated twin reads.
Shown as byte
azure.devices_elasticpools_iothubtenants.c2d.twin.read.success
(count)
The count of all successful back-end-initiated twin reads.
azure.devices_elasticpools_iothubtenants.c2d.twin.update.failure
(count)
The count of all failed back-end-initiated twin updates.
azure.devices_elasticpools_iothubtenants.c2d.twin.update.size
(gauge)
The average min and max size of all successful back-end-initiated twin updates.
Shown as byte
azure.devices_elasticpools_iothubtenants.c2d.twin.update.success
(count)
The count of all successful back-end-initiated twin updates.
azure.devices_elasticpools_iothubtenants.d2c.endpoints.egress.built_in.events
(count)
Number of times messages were successfully written to the built-in endpoint (messages/events)
azure.devices_elasticpools_iothubtenants.d2c.endpoints.egress.event_hubs
(count)
Number of times messages were successfully written to Event Hub endpoints
azure.devices_elasticpools_iothubtenants.d2c.endpoints.egress.service_bus_queues
(count)
Number of times messages were successfully written to Service Bus Queue endpoints
azure.devices_elasticpools_iothubtenants.d2c.endpoints.egress.service_bus_topics
(count)
Number of times messages were successfully written to Service Bus Topic endpoints
azure.devices_elasticpools_iothubtenants.d2c.endpoints.egress.storage
(count)
Number of times messages were successfully written to storage endpoints
azure.devices_elasticpools_iothubtenants.d2c.endpoints.egress.storage.blobs
(count)
Number of blobs written to storage endpoints
azure.devices_elasticpools_iothubtenants.d2c.endpoints.egress.storage.bytes
(gauge)
Amount of data in bytes written to storage endpoints
Shown as byte
azure.devices_elasticpools_iothubtenants.d2c.endpoints.latency.built_in.events
(gauge)
The average latency between message ingress to the IoT hub and message ingress into the built-in endpoint (messages/events) in milliseconds
Shown as millisecond
azure.devices_elasticpools_iothubtenants.d2c.endpoints.latency.event_hubs
(gauge)
The average latency between message ingress to the IoT hub and message ingress into an Event Hub endpoint in milliseconds
Shown as millisecond
azure.devices_elasticpools_iothubtenants.d2c.endpoints.latency.service_bus_queues
(gauge)
The average latency between message ingress to the IoT hub and message ingress into a Service Bus Queue endpoint in milliseconds
Shown as millisecond
azure.devices_elasticpools_iothubtenants.d2c.endpoints.latency.service_bus_topics
(gauge)
The average latency between message ingress to the IoT hub and message ingress into a Service Bus Topic endpoint in milliseconds
Shown as millisecond
azure.devices_elasticpools_iothubtenants.d2c.endpoints.latency.storage
(gauge)
The average latency between message ingress to the IoT hub and message ingress into a storage endpoint in milliseconds
Shown as millisecond
azure.devices_elasticpools_iothubtenants.d2c.telemetry.egress.dropped
(count)
Number of messages dropped because the delivery endpoint was dead
azure.devices_elasticpools_iothubtenants.d2c.telemetry.egress.fallback
(count)
Number of messages written to the fallback endpoint
azure.devices_elasticpools_iothubtenants.d2c.telemetry.egress.invalid
(count)
The count of messages not delivered due to incompatibility with the endpoint
azure.devices_elasticpools_iothubtenants.d2c.telemetry.egress.orphaned
(count)
The count of messages not matching any routes including the fallback route
azure.devices_elasticpools_iothubtenants.d2c.telemetry.egress.success
(count)
Number of times messages were successfully written to endpoints (total)
azure.devices_elasticpools_iothubtenants.d2c.telemetry.ingress.all_protocol
(count)
Number of device-to-cloud telemetry messages attempted to be sent to your IoT hub
azure.devices_elasticpools_iothubtenants.d2c.telemetry.ingress.send_throttle
(count)
Number of throttling errors due to device throughput throttles
azure.devices_elasticpools_iothubtenants.d2c.telemetry.ingress.success
(count)
Number of device-to-cloud telemetry messages sent successfully to your IoT hub
azure.devices_elasticpools_iothubtenants.d2c.twin.read.failure
(count)
The count of all failed device-initiated twin reads.
azure.devices_elasticpools_iothubtenants.d2c.twin.read.size
(gauge)
The average min and max of all successful device-initiated twin reads.
Shown as byte
azure.devices_elasticpools_iothubtenants.d2c.twin.read.success
(count)
The count of all successful device-initiated twin reads.
azure.devices_elasticpools_iothubtenants.d2c.twin.update.failure
(count)
The count of all failed device-initiated twin updates.
azure.devices_elasticpools_iothubtenants.d2c.twin.update.size
(gauge)
The average min and max size of all successful device-initiated twin updates.
Shown as byte
azure.devices_elasticpools_iothubtenants.d2c.twin.update.success
(count)
The count of all successful device-initiated twin updates.
azure.devices_elasticpools_iothubtenants.daily_message_quota_used
(count)
Number of total messages used today. This is a cumulative value that is reset to zero at 00:00 UTC every day.
azure.devices_elasticpools_iothubtenants.device_data_usage
(count)
Bytes transferred to and from any devices connected to IotHub
azure.devices_elasticpools_iothubtenants.devices.connected_devices.all_protocol
(count)
Number of devices connected to your IoT hub
azure.devices_elasticpools_iothubtenants.devices.total_devices
(count)
Number of devices registered to your IoT hub
azure.devices_elasticpools_iothubtenants.jobs.cancel_job.failure
(count)
The count of all failed calls to cancel a job.
azure.devices_elasticpools_iothubtenants.jobs.cancel_job.success
(count)
The count of all successful calls to cancel a job.
azure.devices_elasticpools_iothubtenants.jobs.completed
(count)
The count of all completed jobs.
azure.devices_elasticpools_iothubtenants.jobs.create_direct_method_job.failure
(count)
The count of all failed creation of direct method invocation jobs.
azure.devices_elasticpools_iothubtenants.jobs.create_direct_method_job.success
(count)
The count of all successful creation of direct method invocation jobs.
azure.devices_elasticpools_iothubtenants.jobs.create_twin_update_job.failure
(count)
The count of all failed creation of twin update jobs.
azure.devices_elasticpools_iothubtenants.jobs.create_twin_update_job.success
(count)
The count of all successful creation of twin update jobs.
azure.devices_elasticpools_iothubtenants.jobs.failed
(count)
The count of all failed jobs.
azure.devices_elasticpools_iothubtenants.jobs.list_jobs.failure
(count)
The count of all failed calls to list jobs.
azure.devices_elasticpools_iothubtenants.jobs.list_jobs.success
(count)
The count of all successful calls to list jobs.
azure.devices_elasticpools_iothubtenants.jobs.query_jobs.failure
(count)
The count of all failed calls to query jobs.
azure.devices_elasticpools_iothubtenants.jobs.query_jobs.success
(count)
The count of all successful calls to query jobs.
azure.devices_elasticpools_iothubtenants.tenant_hub.requested_usage_rate
(gauge)
requested usage rate
Shown as percent
azure.devices_elasticpools_iothubtenants.twin_queries.failure
(count)
The count of all failed twin queries.
azure.devices_elasticpools_iothubtenants.twin_queries.result_size
(gauge)
The average min and max of the result size of all successful twin queries.
Shown as byte
azure.devices_elasticpools_iothubtenants.twin_queries.success
(count)
The count of all successful twin queries.
azure.devices_elasticpools.elastic_pool.requested_usage_rate
(gauge)
requested usage rate
Shown as percent
azure.functions.average_memory_working_set
(gauge)
Average memory working set
Shown as byte
azure.functions.bytes_received
(gauge)
Data In
Shown as byte
azure.functions.bytes_sent
(gauge)
Data Out
Shown as byte
azure.functions.connections
(gauge)
Connections
Shown as connection
azure.functions.current_assemblies
(gauge)
Current Assemblies
azure.functions.function_execution_count
(count)
Function Execution Count
azure.functions.function_execution_units
(count)
Function Execution Units
azure.functions.gen_0_garbage_collections
(gauge)
Gen 0 Garbage Collections
azure.functions.gen_1_garbage_collections
(gauge)
Gen 1 Garbage Collections
azure.functions.gen_2_garbage_collections
(gauge)
Gen 2 Garbage Collections
azure.functions.handle_count
(count)
Handle Count
azure.functions.http5xx
(count)
Http Server Errors
azure.functions.io_other_bytes_per_second
(rate)
IO Other Bytes Per Second
Shown as byte
azure.functions.io_other_operations_per_second
(rate)
IO Other Operations Per Second
Shown as operation
azure.functions.io_read_bytes_per_second
(rate)
IO Read Bytes Per Second
Shown as byte
azure.functions.io_read_operations_per_second
(rate)
IO Read Operations Per Second
Shown as operation
azure.functions.io_write_bytes_per_second
(rate)
IO Write Bytes Per Second
Shown as byte
azure.functions.io_write_operations_per_second
(rate)
IO Write Operations Per Second
Shown as operation
azure.functions.memory_working_set
(gauge)
Memory working set
Shown as byte
azure.functions.private_bytes
(gauge)
Private Bytes
Shown as byte
azure.functions.thread_count
(count)
Thread Count
Shown as thread
azure.functions.total_app_domains_unloaded
(gauge)
Total App Domains Unloaded
azure.functions.total_app_domains
(gauge)
Total App Domains
azure.insights_autoscalesettings.metric_threshold
(count)
The configured autoscale threshold when autoscale ran.
azure.insights_autoscalesettings.observed_capacity
(count)
The capacity reported to autoscale when it executed.
azure.insights_autoscalesettings.observed_metric_value
(count)
The value computed by autoscale when executed
azure.insights_autoscalesettings.scale_actions_initiated
(count)
The direction of the scale operation.
azure.locationbasedservices_accounts.latency
(gauge)
Duration of API calls
Shown as millisecond
azure.network_connections.bits_in_per_second
(rate)
Bits ingressing Azure per second
Shown as bit
azure.network_connections.bits_out_per_second
(rate)
Bits egressing Azure per second
Shown as bit
azure.network_connections.status
(gauge)
Status of Azure Network Connections metrics
azure.network_dnszones.query_volume
(count)
Number of queries served for a DNS zone
azure.network_dnszones.record_set_capacity_utilization
(gauge)
Percent of Record Set capacity utilized by a DNS zone
Shown as percent
azure.network_dnszones.record_set_count
(count)
Number of Record Sets in a DNS zone
azure.network_networkwatchers_connectionmonitors.average_roundtrip_ms
(gauge)
Average network round-trip time (ms) for connectivity monitoring probes sent between source and destination
Shown as millisecond
azure.network_networkwatchers_connectionmonitors.probes_failed_percent
(gauge)
% of connectivity monitoring probes failed
Shown as percent
azure.network_trafficmanagerprofiles.qps_by_endpoint
(count)
Number of times a Traffic Manager endpoint was returned in the given time frame
azure.network_virtualnetworkgateways.tunnel_average_bandwidth
(rate)
Average bandwidth of a tunnel in bytes per second
Shown as byte
azure.network_virtualnetworkgateways.tunnel_egress_bytes
(gauge)
Outgoing bytes of a tunnel
Shown as byte
azure.network_virtualnetworkgateways.tunnel_egress_packet_drop_tsmismatch
(count)
Outgoing packet drop count from traffic selector mismatch of a tunnel
azure.network_virtualnetworkgateways.tunnel_egress_packets
(count)
Outgoing packet count of a tunnel
azure.network_virtualnetworkgateways.tunnel_ingress_bytes
(gauge)
Incoming bytes of a tunnel
Shown as byte
azure.network_virtualnetworkgateways.tunnel_ingress_packet_drop_tsmismatch
(count)
Incoming packet drop count from traffic selector mismatch of a tunnel
azure.network_virtualnetworkgateways.tunnel_ingress_packets
(count)
Incoming packet count of a tunnel
azure.operationalinsights_workspaces.status
(gauge)
Status of Azure Operational Insights
azure.powerbidedicated_capacities.query_duration
(gauge)
DAX Query duration in last interval
Shown as millisecond
azure.powerbidedicated_capacities.query_pool_job_queue_length
(count)
Number of jobs in the queue of the query thread pool.
azure.servicefabric_clusters.status
(gauge)
Status of Azure Service Fabric
azure.storage.availability
(gauge)
The percentage of availability for the storage service or the specified API operation.
Shown as percent
azure.storage.egress
(gauge)
The amount of egress data, in bytes.
Shown as byte
azure.storage.ingress
(gauge)
The amount of ingress data, in bytes.
Shown as byte
azure.storage.status
(gauge)
Status of Azure Storage Integration
azure.storage.success_e2_e_latency
(gauge)
The average end-to-end latency of successful requests made to a storage service or the specified API operation, in milliseconds.
Shown as millisecond
azure.storage.success_server_latency
(gauge)
The average latency used by Azure Storage to process a successful request, in milliseconds.
Shown as millisecond
azure.storage.transactions
(count)
The number of requests made to a storage service or the specified API operation.
azure.storage.used_capacity
(gauge)
Account used capacity
Shown as byte
azure.web_sites_slots.app_connections
(count)
Connections
azure.web_sites_slots.average_memory_working_set
(gauge)
Average memory working set
Shown as byte
azure.web_sites_slots.average_response_time
(count)
Average Response Time
Shown as second
azure.web_sites_slots.bytes_received
(gauge)
Data In
Shown as byte
azure.web_sites_slots.bytes_sent
(gauge)
Data Out
Shown as byte
azure.web_sites_slots.cpu_time
(gauge)
CPU Time
Shown as second
azure.web_sites_slots.function_execution_count
(count)
Function Execution Count
azure.web_sites_slots.function_execution_units
(count)
Function Execution Units
azure.web_sites_slots.handles
(count)
Handle Count
azure.web_sites_slots.http101
(count)
Http 101
azure.web_sites_slots.http2xx
(count)
Http 2xx
azure.web_sites_slots.http3xx
(count)
Http 3xx
azure.web_sites_slots.http401
(count)
Http 401
azure.web_sites_slots.http403
(count)
Http 403
azure.web_sites_slots.http404
(count)
Http 404
azure.web_sites_slots.http406
(count)
Http 406
azure.web_sites_slots.http4xx
(count)
Http 4xx
azure.web_sites_slots.http5xx
(count)
Http Server Errors
azure.web_sites_slots.memory_working_set
(gauge)
Memory working set
Shown as byte
azure.web_sites_slots.requests
(count)
Requests
azure.web_sites_slots.threads
(count)
Thread Count

Events

The Azure integration sends all your Azure events to your Datadog Event stream.

Service Checks

The Azure integration does not include any service checks.

Troubleshooting

Need help? Contact Datadog support.

Further Reading