All Integrations / Azure Monitor and Azure Data Explorer Integration

Azure Monitor and Azure Data Explorer Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

Get This Integration for Free
info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider <a href="/integrations/azure_monitor-influxdb/">Azure Monitor and InfluxDB</a>.

5B+

Telegraf downloads

#1

Time series database
Source: DB Engines

1B+

Downloads of InfluxDB

2,800+

Contributors

Table of Contents

Useful Links

Documentation

Telegraf Quickstart Training

Infrastructure Monitoring with Telegraf

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Input and output integration overview

<p>Gather metrics from Azure resources using the Azure Monitor API.</p>

<p>The Azure Data Explorer plugin allows integration of metrics collection with Azure Data Explorer, enabling users to analyze and query their telemetry data efficiently. With this plugin, users can configure ingestion settings to suit their needs and leverage Azure’s powerful analytical capabilities.</p>

Integration details

Azure Monitor

<p>The Azure Monitor Telegraf plugin is specifically designed for gathering metrics from various Azure resources using the Azure Monitor API. Users must provide specific credentials such as <code>client_id</code>, <code>client_secret</code>, <code>tenant_id</code>, and <code>subscription_id</code> to authenticate and gain access to their Azure resources. Additionally, the plugin supports functionality to collect metrics from both individual resources and resource groups or subscriptions, allowing for flexible and scalable metric collection tailored to user needs. This plugin is ideal for organizations leveraging Azure cloud infrastructure, providing crucial insights into resource performance and utilization over time, facilitating proactive management and optimization of cloud resources.</p>

Azure Data Explorer

<p>The Azure Data Explorer plugin allows users to write metrics, logs, and time series data collected from various Telegraf input plugins into Azure Data Explorer, Azure Synapse, and Real-Time Analytics in Fabric. This integration serves as a bridge, allowing applications and services to monitor their performance metrics or logs efficiently. Azure Data Explorer is optimized for analytics over large volumes of diverse data types, making it an excellent choice for real-time analytics and monitoring solutions in cloud environments. The plugin empowers users to configure metrics ingestion based on their requirements, define table schemas dynamically, and set various ingestion methods while retaining flexibility regarding roles and permissions needed for database operations. This supports scalable and secure monitoring setups for modern applications that utilize cloud services.</p>

Configuration

Azure Monitor

<pre><code class="language-toml"># Gather Azure resources metrics from Azure Monitor API [[inputs.azure_monitor]] # can be found under Overview-&gt;Essentials in the Azure portal for your application/service subscription_id = "&lt;<SUBSCRIPTION_ID>&gt;" # can be obtained by registering an application under Azure Active Directory client_id = "&lt;<CLIENT_ID>&gt;" # can be obtained by registering an application under Azure Active Directory. # If not specified Default Azure Credentials chain will be attempted: # - Environment credentials (AZURE_*) # - Workload Identity in Kubernetes cluster # - Managed Identity # - Azure CLI auth # - Developer Azure CLI auth client_secret = "&lt;<CLIENT_SECRET>&gt;" # can be found under Azure Active Directory-&gt;Properties tenant_id = "&lt;<TENANT_ID>&gt;" # Define the optional Azure cloud option e.g. AzureChina, AzureGovernment or AzurePublic. The default is AzurePublic. # cloud_option = "AzurePublic" # resource target #1 to collect metrics from [[inputs.azure_monitor.resource_target]] # can be found under Overview-&gt;Essentials-&gt;JSON View in the Azure portal for your application/service # must start with 'resourceGroups/...' ('/subscriptions/xxxxxxxx-xxxx-xxxx-xxx-xxxxxxxxxxxx' # must be removed from the beginning of Resource ID property value) resource_id = "&lt;<RESOURCE_ID>&gt;" # the metric names to collect # leave the array empty to use all metrics available to this resource metrics = [ "&lt;<METRIC>&gt;", "&lt;<METRIC>&gt;" ] # metrics aggregation type value to collect # can be 'Total', 'Count', 'Average', 'Minimum', 'Maximum' # leave the array empty to collect all aggregation types values for each metric aggregations = [ "&lt;<AGGREGATION>&gt;", "&lt;<AGGREGATION>&gt;" ] # resource target #2 to collect metrics from [[inputs.azure_monitor.resource_target]] resource_id = "&lt;<RESOURCE_ID>&gt;" metrics = [ "&lt;<METRIC>&gt;", "&lt;<METRIC>&gt;" ] aggregations = [ "&lt;<AGGREGATION>&gt;", "&lt;<AGGREGATION>&gt;" ] # resource group target #1 to collect metrics from resources under it with resource type [[inputs.azure_monitor.resource_group_target]] # the resource group name resource_group = "&lt;<RESOURCE_GROUP_NAME>&gt;" # defines the resources to collect metrics from [[inputs.azure_monitor.resource_group_target.resource]] # the resource type resource_type = "&lt;<RESOURCE_TYPE>&gt;" metrics = [ "&lt;<METRIC>&gt;", "&lt;<METRIC>&gt;" ] aggregations = [ "&lt;<AGGREGATION>&gt;", "&lt;<AGGREGATION>&gt;" ] # defines the resources to collect metrics from [[inputs.azure_monitor.resource_group_target.resource]] resource_type = "&lt;<RESOURCE_TYPE>&gt;" metrics = [ "&lt;<METRIC>&gt;", "&lt;<METRIC>&gt;" ] aggregations = [ "&lt;<AGGREGATION>&gt;", "&lt;<AGGREGATION>&gt;" ] # resource group target #2 to collect metrics from resources under it with resource type [[inputs.azure_monitor.resource_group_target]] resource_group = "&lt;<RESOURCE_GROUP_NAME>&gt;" [[inputs.azure_monitor.resource_group_target.resource]] resource_type = "&lt;<RESOURCE_TYPE>&gt;" metrics = [ "&lt;<METRIC>&gt;", "&lt;<METRIC>&gt;" ] aggregations = [ "&lt;<AGGREGATION>&gt;", "&lt;<AGGREGATION>&gt;" ] # subscription target #1 to collect metrics from resources under it with resource type [[inputs.azure_monitor.subscription_target]] resource_type = "&lt;<RESOURCE_TYPE>&gt;" metrics = [ "&lt;<METRIC>&gt;", "&lt;<METRIC>&gt;" ] aggregations = [ "&lt;<AGGREGATION>&gt;", "&lt;<AGGREGATION>&gt;" ] # subscription target #2 to collect metrics from resources under it with resource type [[inputs.azure_monitor.subscription_target]] resource_type = "&lt;<RESOURCE_TYPE>&gt;" metrics = [ "&lt;<METRIC>&gt;", "&lt;<METRIC>&gt;" ] aggregations = [ "&lt;<AGGREGATION>&gt;", "&lt;<AGGREGATION>&gt;" ] &lt;/code&gt;&lt;/pre&gt; </AGGREGATION></AGGREGATION></METRIC></METRIC></RESOURCE_TYPE></AGGREGATION></AGGREGATION></METRIC></METRIC></RESOURCE_TYPE></AGGREGATION></AGGREGATION></METRIC></METRIC></RESOURCE_TYPE></RESOURCE_GROUP_NAME></AGGREGATION></AGGREGATION></METRIC></METRIC></RESOURCE_TYPE></AGGREGATION></AGGREGATION></METRIC></METRIC></RESOURCE_TYPE></RESOURCE_GROUP_NAME></AGGREGATION></AGGREGATION></METRIC></METRIC></RESOURCE_ID></AGGREGATION></AGGREGATION></METRIC></METRIC></RESOURCE_ID></TENANT_ID></CLIENT_SECRET></CLIENT_ID></SUBSCRIPTION_ID></code></pre>

Azure Data Explorer

<pre><code class="language-toml">[[outputs.azure_data_explorer]] ## The URI property of the Azure Data Explorer resource on Azure ## ex: endpoint_url = https://myadxresource.australiasoutheast.kusto.windows.net endpoint_url = "" ## The Azure Data Explorer database that the metrics will be ingested into. ## The plugin will NOT generate this database automatically, it's expected that this database already exists before ingestion. ## ex: "exampledatabase" database = "" ## Timeout for Azure Data Explorer operations # timeout = "20s" ## Type of metrics grouping used when pushing to Azure Data Explorer. ## Default is "TablePerMetric" for one table per different metric. ## For more information, please check the plugin README. # metrics_grouping_type = "TablePerMetric" ## Name of the single table to store all the metrics (Only needed if metrics_grouping_type is "SingleTable"). # table_name = "" ## Creates tables and relevant mapping if set to true(default). ## Skips table and mapping creation if set to false, this is useful for running Telegraf with the lowest possible permissions i.e. table ingestor role. # create_tables = true ## Ingestion method to use. ## Available options are ## - managed -- streaming ingestion with fallback to batched ingestion or the "queued" method below ## - queued -- queue up metrics data and process sequentially # ingestion_type = "queued" </code></pre>

Input and output integration examples

Azure Monitor

<ol> <li> <p><strong>Dynamic Resource Monitoring</strong>: Use the Azure Monitor plugin to dynamically gather metrics from Azure resources based on specific criteria like tags or resource types. Organizations can automate the process of loading and unloading resource metrics, enabling better performance tracking and optimization based on resource utilization patterns.</p> </li> <li> <p><strong>Multi-Cloud Monitoring Integration</strong>: Integrate metrics collected from Azure Monitor with other cloud providers using a centralized monitoring solution. This allows organizations to view and analyze performance data across multiple cloud deployments, providing a holistic overview of resource performance and costs, and streamlining operations.</p> </li> <li> <p><strong>Anomaly Detection and Alerting</strong>: Leverage the metrics gathered via the Azure Monitor plugin in conjunction with machine learning algorithms to detect anomalies in resource utilization. By establishing baseline performance metrics and automatically alerting on deviations, organizations can mitigate risks and address performance issues before they escalate.</p> </li> <li> <p><strong>Historical Performance Analysis</strong>: Use the collected Azure metrics to conduct historical analysis by feeding the data into a data warehousing solution. This enables organizations to track trends over time, allowing for detailed reporting and decision-making based on historical performance data.</p> </li> </ol>

Azure Data Explorer

<ol> <li> <p><strong>Real-Time Monitoring Dashboard</strong>: By integrating metrics from various services into Azure Data Explorer using this plugin, organizations can build comprehensive dashboards that reflect real-time performance metrics. This allows teams to respond proactively to performance issues and optimize system health without delay.</p> </li> <li> <p><strong>Centralized Log Management</strong>: Utilize Azure Data Explorer to consolidate logs from multiple applications and services. By utilizing the plugin, organizations can streamline their log analysis processes, making it easier to search, filter, and derive insights from historical data accumulated over time.</p> </li> <li> <p><strong>Data-Driven Alerting Systems</strong>: Enhance monitoring capabilities by configuring alerts based on metrics sent via this plugin. Organizations can set thresholds and automate incident responses, significantly reducing downtime and improving the reliability of critical operations.</p> </li> <li> <p><strong>Machine Learning Model Training</strong>: By leveraging the data sent to Azure Data Explorer, organizations can perform large-scale analytics and prepare the data for feeding into machine learning models. This plugin enables the structuring of data that can subsequently be used for predictive analytics, leading to enhanced decision-making capabilities.</p> </li> </ol>

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.

Useful Links

Documentation

Telegraf Quickstart Training

Infrastructure Monitoring with Telegraf

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Related Integrations

HTTP and InfluxDB Integration

The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.

View Integration

Kafka and InfluxDB Integration

This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.

View Integration

Kinesis and InfluxDB Integration

The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.

View Integration

Start building now

Download Telegraf today or learn more about InfluxDB.

telegraf Get started with InfluxDB
Product & Solutions
Developers
Company

548 Market St, PMB 77953
San Francisco, California 94104

© 2025 InfluxData Inc. All Rights Reserved.

Legal Security Cookie Policy Comparison