--- title: Azure Data Explorer description: Track key Azure Data Explorer metrics. breadcrumbs: Docs > Integrations > Azure Data Explorer --- # Azure Data Explorer ## Overview{% #overview %} Azure Data Explorer is a highly scalable and secure analytics service that enables you to do rich exploration of structured and unstructured data for instant insights. Optimized for ad-hoc queries, Azure Data Explorer enables data exploration over raw, structured, and semi-structured data delivering fast time to insight. Use Datadog to monitor your Azure Data Explorer performance and utilization in context with the rest of your applications and infrastructure. Get metrics from Azure Data Explorer to: - Track ingestion, processing, and latency performance of your Data Explorer instances. - Monitor the utilization of your Data Explorer compute, memory, and network resources. ## Setup{% #setup %} ### Installation{% #installation %} If you haven't already, set up the [Microsoft Azure integration](https://docs.datadoghq.com/integrations/azure.md) first. There are no other installation steps. ## Data Collected{% #data-collected %} ### Metrics{% #metrics %} | | | | | **azure.kusto\_clusters.batch\_blob\_count**(gauge) | Number of data sources in an aggregated batch for ingestion. | | **azure.kusto\_clusters.batch\_duration**(gauge) | Duration of the aggregation phase in the ingestion flow.*Shown as second* | | **azure.kusto\_clusters.batches\_processed**(count) | Number of batches aggregated for ingestion. Batching Type: whether the batch reached batching time; data size or number of files limit set by batching policy. | | **azure.kusto\_clusters.batch\_size**(gauge) | Uncompressed expected data size in an aggregated batch for ingestion.*Shown as byte* | | **azure.kusto\_clusters.blobs\_dropped**(count) | Number of blobs permanently rejected by a component. | | **azure.kusto\_clusters.blobs\_processed**(count) | Number of blobs processed by a component. | | **azure.kusto\_clusters.blobs\_received**(count) | Number of blobs received from input stream by a component. | | **azure.kusto\_clusters.cache\_utilization**(gauge) | Utilization level in the cluster scope.*Shown as percent* | | **azure.kusto\_clusters.cache\_utilization\_factor**(gauge) | Percentage difference between the current number of instances and the optimal number of instances (per cache utilization).*Shown as percent* | | **azure.kusto\_clusters.continuous\_export\_max\_lateness\_minutes**(gauge) | Lateness (in minutes) reported by the continuous export jobs in the cluster. | | **azure.kusto\_clusters.continuous\_export\_num\_of\_records\_exported**(count) | Number of records exported; fired for every storage artifact written during the export operation. | | **azure.kusto\_clusters.continuous\_export\_pending\_count**(gauge) | Number of pending continuous export jobs ready for execution. | | **azure.kusto\_clusters.continuous\_export\_result**(count) | Indicates whether Continuous Export succeeded or failed. | | **azure.kusto\_clusters.cpu**(gauge) | CPU utilization level.*Shown as percent* | | **azure.kusto\_clusters.discovery\_latency**(gauge) | Reported by data connections (if exist). Time in seconds from when a message is enqueued or event is created until it is discovered by data connection. This time is not included in the Azure Data Explorer total ingestion duration.*Shown as second* | | **azure.kusto\_clusters.events\_dropped**(count) | Number of events dropped permanently by data connection. An Ingestion result metric with a failure reason will be sent. | | **azure.kusto\_clusters.events\_processed**(count) | Number of events processed by the cluster. | | **azure.kusto\_clusters.events\_processed\_for\_event\_hubs**(count) | Number of events processed by the cluster when ingesting from Event/IoT Hub. | | **azure.kusto\_clusters.events\_received**(count) | Number of events received by data connection. | | **azure.kusto\_clusters.export\_utilization**(gauge) | Export utilization.*Shown as percent* | | **azure.kusto\_clusters.ingestion\_latency\_in\_seconds**(gauge) | Latency of data ingested; from the time the data was received in the cluster until it's ready for query. The ingestion latency period depends on the ingestion scenario.*Shown as second* | | **azure.kusto\_clusters.ingestion\_result**(count) | Total number of sources that either failed or succeeded to be ingested. Splitting the metric by status; you can get detailed information about the status of the ingestion operations. | | **azure.kusto\_clusters.ingestion\_utilization**(gauge) | Ratio of used ingestion slots in the cluster.*Shown as percent* | | **azure.kusto\_clusters.ingestion\_volume\_in\_mb**(count) | Overall volume of ingested data to the cluster.*Shown as byte* | | **azure.kusto\_clusters.instance\_count**(gauge) | Total instance count. | | **azure.kusto\_clusters.keep\_alive**(gauge) | Sanity check indicates the cluster responds to queries. | | **azure.kusto\_clusters.materialized\_view\_age\_minutes**(gauge) | Materialized view age in minutes. | | **azure.kusto\_clusters.materialized\_view\_age\_seconds**(gauge) | Materialized view age in seconds.*Shown as second* | | **azure.kusto\_clusters.materialized\_view\_data\_loss**(gauge) | Indicates potential data loss in materialized view. | | **azure.kusto\_clusters.materialized\_view\_extents\_rebuild**(gauge) | Number of extents rebuild. | | **azure.kusto\_clusters.materialized\_view\_health**(gauge) | Health of the materialized view (1 for healthy; 0 for non-healthy). | | **azure.kusto\_clusters.materialized\_view\_records\_in\_delta**(gauge) | Number of records in the non-materialized part of the view. | | **azure.kusto\_clusters.materialized\_view\_result**(gauge) | Result of the materialization process. | | **azure.kusto\_clusters.query\_duration**(gauge) | Queriesduration in seconds.*Shown as millisecond* | | **azure.kusto\_clusters.query\_result**(count) | Total number of queries. | | **azure.kusto\_clusters.queue\_length**(gauge) | Number of pending messages in a component's queue. | | **azure.kusto\_clusters.queue\_oldest\_message**(gauge) | Time in seconds from when the oldest message in queue was inserted. | | **azure.kusto\_clusters.received\_data\_size\_bytes**(gauge) | Size of data received by data connection. This is the size of the data stream; or of raw data size if provided.*Shown as byte* | | **azure.kusto\_clusters.stage\_latency**(gauge) | Cumulative time from when a message is discovered until it is received by the reporting component for processing (discovery time is set when message is enqueued for ingestion queue; or when discovered by data connection).*Shown as second* | | **azure.kusto\_clusters.streaming\_ingest\_data\_rate**(gauge) | Streaming ingest data rate (MB per second). | | **azure.kusto\_clusters.streaming\_ingest\_duration**(gauge) | Streaming ingest duration in milliseconds.*Shown as millisecond* | | **azure.kusto\_clusters.streaming\_ingest\_results**(count) | Streaming ingest result. | | **azure.kusto\_clusters.total\_number\_of\_concurrent\_queries**(gauge) | Total number of concurrent queries. | | **azure.kusto\_clusters.total\_number\_of\_extents**(gauge) | Total number of data extents. | | **azure.kusto\_clusters.total\_number\_of\_throttled\_commands**(count) | Total number of throttled commands. | | **azure.kusto\_clusters.total\_number\_of\_throttled\_queries**(gauge) | Total number of throttled queries. | | **azure.kusto\_clusters.weak\_consistency\_latency**(gauge) | Max latency between the previous metadata sync and the next one (in db/node scope).*Shown as second* | | **azure.kusto\_clusters.count**(gauge) | Count of Kusto clusters. | ### Events{% #events %} The Azure Data Explorer integration does not include any events. ### Service Checks{% #service-checks %} The Azure Data Explorer integration does not include any service checks. ## Troubleshooting{% #troubleshooting %} Need help? Contact [Datadog support](https://docs.datadoghq.com/help/).