Azure Monitor and SigNoz Integration

Input and output integration overview

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

<p>This configuration turns any Telegraf agent into a Remote Write publisher for SigNoz, streaming rich metrics straight into the SigNoz backend with a single URL change.</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>

SigNoz

<p>SigNoz is an open source observability platform that stores metrics, traces, and logs. When you deploy SigNoz, its <strong>signoz-otel-collector-metrics</strong> service exposes a Prometheus Remote Write receiver (default <strong>:13133/api/v1/write</strong>). By configuring Telegraf’s Prometheus plugin to point at this endpoint, you can push any Telegraf collected metrics, SNMP counters, cloud services, or business KPIs—directly into SigNoz. The plugin natively serializes metrics in the Remote Write protobuf format, supports external labels, metadata export, retries, and TLS or bearer-token auth, so it fits zero-trust and multi-tenant SigNoz clusters. Inside SigNoz, the data lands in ClickHouse tables that back Metrics Explorer, alert rules, and unified dashboards. This approach lets organizations unify Prometheus and OTLP pipelines, enables long-term retention powered by ClickHouse compression, and avoids vendor lock-in while retaining PromQL-style queries.</p>

Configuration

Azure Monitor

SigNoz

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>

SigNoz

<ol> <li> <p><strong>Multi-Cluster Federated Monitoring</strong>: Drop a Telegraf DaemonSet into each Kubernetes cluster, tag metrics with <code>cluster=&lt;name&gt;</code>, and Remote Write them to a central SigNoz instance. Ops teams get a single PromQL window across prod, staging, and edge clusters without running Thanos sidecars.</p> </li> <li> <p><strong>Factory-Floor Edge Gateway</strong>: A rugged Intel NUC on the shop floor runs Telegraf to scrape Modbus PLCs and environmental sensors. It batches readings every 5 seconds and pushes them over an intermittent 4G link to SigNoz SaaS. ClickHouse compression keeps costs low while AI-based outlier detection in SigNoz flags overheating motors before failure.</p> </li> <li> <p><strong>SaaS Usage Metering</strong>: Telegraf runs alongside each micro-service, exporting per-tenant counters (<code>api_calls</code>, <code>gigabytes_processed</code>). Remote Write streams the data to SigNoz where a scheduled ClickHouse materialized view aggregates usage for monthly billing—no separate metering stack required.</p> </li> <li> <p><strong>Autoscaling Feedback Loop</strong>: Combine Telegraf’s Kubernetes input with the Remote Write output to publish granular pod CPU and queue-length metrics into SigNoz. A custom SigNoz alert fires when P95 latency breaches 200 ms and a GitOps controller reads that alert to trigger a HorizontalPodAutoscaler tweak—closing the loop between observability and automation.</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.