<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Installation on Netdata</title><link>https://www.netdata.cloud/tags/installation/</link><description>Recent content in Installation on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 13 Aug 2026 08:45:56 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/installation/index.xml" rel="self" type="application/rss+xml"/><item><title>Netdata Best Practices</title><link>https://www.netdata.cloud/blog/netdata-best-practices/</link><pubDate>Fri, 03 Nov 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/netdata-best-practices/</guid><description>&lt;p>Effective &lt;strong>system monitoring&lt;/strong> is non-negotiable in today&amp;rsquo;s complex IT environments. Netdata offers real-time performance and health monitoring with precision and granularity. But the key to harnessing its full potential lies in the optimization of your setup. Let’s ensure you are not just collecting data, but doing it in the most optimal way while gaining actionable insights from it.&lt;/p>
&lt;p>The starting point for optimization is a robust setup. Netdata is engineered for minimal footprint and can run on a wide range of hardware—from IoT devices to powerful servers. Time for a deep dive into each of these key areas and what the best practices you should follow, if you are serious about monitoring and optimizing your Netdata monitoring setup:&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></channel></rss>