<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure Monitor on Netdata</title><link>https://www.netdata.cloud/tags/azure-monitor/</link><description>Recent content in Azure Monitor on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/azure-monitor/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Monitor Collector: Monitor Azure Infrastructure</title><link>https://www.netdata.cloud/blog/azure-monitor/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/azure-monitor/</guid><description>&lt;p>&lt;img src="../images/azure-monitor-collector.svg" alt="Azure Monitor Collector: Monitor Your Entire Azure Infrastructure From Netdata">&lt;/p>
&lt;p>If you&amp;rsquo;re running infrastructure on Azure, you&amp;rsquo;ve probably dealt with the split between your Azure-native monitoring and the rest of your stack. Your VMs, databases, and Kubernetes clusters generate platform metrics through Azure Monitor, but those metrics live in a separate world from the OS-level, application, and on-prem metrics you&amp;rsquo;re already watching in Netdata. You end up checking two (or more) places during incidents, building mental bridges between dashboards that don&amp;rsquo;t talk to each other.&lt;/p></description></item><item><title>Netdata vs Azure Monitor | Monitoring Tools Comparison</title><link>https://www.netdata.cloud/comparisons/azuremonitor/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/comparisons/azuremonitor/</guid><description/></item></channel></rss>