<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Collectors on Netdata</title><link>https://www.netdata.cloud/tags/collectors/</link><description>Recent content in Collectors on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/collectors/index.xml" rel="self" type="application/rss+xml"/><item><title>NVIDIA DCGM Collector: Deep GPU Monitoring For AI</title><link>https://www.netdata.cloud/blog/nvidia-dcgm-monitoring/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/nvidia-dcgm-monitoring/</guid><description>&lt;p>&lt;img src="../images/dcgm-collector.svg" alt="NVIDIA DCGM Collector: Deep GPU Monitoring for Data Center and AI Infrastructure">&lt;/p>
&lt;p>GPU infrastructure is expensive and increasingly central to production workloads. Whether you&amp;rsquo;re running ML training jobs, inference serving, video transcoding, or HPC workloads, understanding what your GPUs are actually doing, and what&amp;rsquo;s going wrong when performance degrades, is not optional. The problem is that NVIDIA&amp;rsquo;s Data Center GPU Manager (DCGM) exposes an enormous amount of telemetry, but getting that data into a monitoring system in a useful, organized way has traditionally required significant setup and custom dashboarding work.&lt;/p></description></item><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>Nagios Plugins: Run Existing Checks &amp; Custom Scripts</title><link>https://www.netdata.cloud/blog/nagios-plugins/</link><pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/nagios-plugins/</guid><description>&lt;p>A lot of teams have a collection of Nagios plugins and custom monitoring scripts that have been running reliably for years. Some are standard community plugins for checking disk health or SSL certificate expiry. Others are homegrown Bash or Python scripts that check something very specific to the business: whether an API endpoint returns the right payload, whether a batch job completed on time, whether a queue depth is within bounds. These scripts work, they&amp;rsquo;re battle-tested, and nobody wants to rewrite them.&lt;/p></description></item><item><title>Secrets Management: Remove Credentials From Configs</title><link>https://www.netdata.cloud/blog/secrets-management/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/secrets-management/</guid><description>&lt;p>If you&amp;rsquo;re running Netdata collectors that connect to databases, APIs, or other authenticated services, there&amp;rsquo;s a good chance you have passwords sitting in plain-text configuration files right now. It works, but it&amp;rsquo;s the kind of thing that makes security teams nervous and makes credential rotation painful. Every password change means editing config files and restarting collectors.&lt;/p>
&lt;p>Netdata now supports secrets management natively. Instead of putting credentials directly in your collector configurations, you reference them using a resolver syntax, and Netdata resolves the actual values at runtime from whatever source you choose: environment variables, files on disk, the output of a command, or a centralized secret store like HashiCorp Vault or AWS Secrets Manager.&lt;/p></description></item><item><title>Introducing Netdata's Dynamic Configuration Manager</title><link>https://www.netdata.cloud/blog/netdata-dynamic-configuration-manager/</link><pubDate>Wed, 05 Jun 2024 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/netdata-dynamic-configuration-manager/</guid><description>&lt;p>We are thrilled to unveil the latest addition to the Netdata platform: the Dynamic Configuration Manager. This powerful new feature revolutionizes how you manage your monitoring and alerting configurations, making it easier and more efficient than ever before.&lt;/p>
&lt;!--truncate-->
&lt;h2 id="key-features-of-the-dynamic-configuration-manager">&lt;strong>Key Features of the Dynamic Configuration Manager&lt;/strong>&lt;/h2>
&lt;ol>
&lt;li>Create and Modify Alerts from Every Chart
&lt;ul>
&lt;li>You can now create and modify alerts directly from any chart on your dashboard or from the dedicated Alerts tab. This streamlined process allows for quick adjustments and ensures your monitoring is always aligned with your current needs.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Configure Collectors from the Integrations Section on the Dashboard
&lt;ul>
&lt;li>Currently available for go.d collectors, this feature lets you configure collectors straight from the Integrations section. This means you can quickly identify what Netdata can monitor and set up your configurations in one go, without having to dig through multiple settings pages.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Submit Configurations to Multiple Nodes with One Click
&lt;ul>
&lt;li>Managing configurations across a large infrastructure can be time-consuming. With the Dynamic Configuration Manager, you can now submit configurations to multiple nodes simultaneously, saving you valuable time and effort.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Construct and Copy Configurations for IaC Solutions
&lt;ul>
&lt;li>For those using Infrastructure as Code (IaC) solutions, this feature allows you to construct and copy configurations easily, integrating them into your IaC workflows. This ensures your configurations are consistent and reproducible across different environments.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ol>
&lt;h2 id="how-to-use-the-dynamic-configuration-manager">&lt;strong>How to Use the Dynamic Configuration Manager&lt;/strong>&lt;/h2>
&lt;p>To help you get started with the Dynamic Configuration Manager, we’ve put together a quick guide using the Netdata demo environment.&lt;/p></description></item><item><title>Remote UNIX System Monitoring Using Net-SNMP</title><link>https://www.netdata.cloud/blog/remote-unix-monitoring-with-net-snmp/</link><pubDate>Wed, 12 Apr 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/remote-unix-monitoring-with-net-snmp/</guid><description>&lt;p>&lt;img src="../2023-04-12-remote-unix-monitoring-with-net-snmp/img/img.jpg" alt="img">&lt;/p>
&lt;p>Need to monitor a UNIX-like system, but can’t install Netdata on it? With our SNMP collector and Net-SNMP,
you can get basic system information with just a bit of relatively quick and easy configuration.&lt;/p>
&lt;!-- truncate -->
&lt;h2 id="what-is-snmp">What is SNMP?&lt;/h2>
&lt;p>The Simple Network Management Protocol, commonly known as SNMP, is a relatively lightweight protocol designed for
monitoring and configuration management for network appliances like switches, routers or gateways. However, it can also
be used for those purposes on almost any UNIX-like system thanks to the &lt;a href="http://www.net-snmp.org/">Net-SNMP project&lt;/a>.&lt;/p></description></item><item><title>Upcoming Changes to Plugins in Native Packages</title><link>https://www.netdata.cloud/blog/split-plugin-packages/</link><pubDate>Wed, 15 Mar 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/split-plugin-packages/</guid><description>&lt;p>At Netdata, we’re committed to trying to make Netdata work as well as possible for our users. Sometimes though,
that means changing things in ways that aren’t exactly seamless. Such a change is coming soon for users of our
native DEB and RPM packages, and this blog post will explain what’s happening, why we’re doing it, and what
it means for our users.&lt;/p>
&lt;!-- truncate -->
&lt;h2 id="whats-changing">What’s changing?&lt;/h2>
&lt;p>Starting shortly after the v1.39.0 release of the Netdata Agent, we will be splitting most of our external
data collection plugins out to their own individual packages instead of bundling them all in the main &lt;code>netdata&lt;/code>
package. We already have this type of split for our CUPS and FreeIPMI plugins, and this new change will extend
that to also provide separate packages for the following plugins:&lt;/p></description></item><item><title>Using Pandas In Python: Data Analysis &amp; Performance Insights</title><link>https://www.netdata.cloud/blog/pandas-python/</link><pubDate>Wed, 19 Oct 2022 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/pandas-python/</guid><description>&lt;p>Netdata just got a &lt;a href="https://learn.netdata.cloud/docs/agent/collectors/python.d.plugin/pandas" target="_blank" rel="noopener">Pandas collector&lt;/a>.&lt;/p>
&lt;!--truncate-->
&lt;p>Pandas is a de-facto standard in reading and processing most types of structured data in Python so if you have some csv/json/xml data, either locally or via some HTTP endpoint, containing metrics you&amp;rsquo;d like to monitor, chances are you can now easily do this by leveraging the Pandas collector without having to develop your own custom collector as you might have in the past.&lt;/p></description></item></channel></rss>