<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on Netdata</title><link>https://www.netdata.cloud/tags/linux/</link><description>Recent content in Linux on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 18:50:41 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux Monitoring Software With Per-Second Metrics</title><link>https://www.netdata.cloud/solutions/technologies/linux-monitoring/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/solutions/technologies/linux-monitoring/</guid><description>Netdata delivers complete Linux monitoring with per-second granularity, edge-based ML anomaly detection, and zero-pipeline logs - all with zero configuration and predictable per-node pricing.</description></item><item><title>Docker Monitoring Tool With Unlimited Containers</title><link>https://www.netdata.cloud/solutions/technologies/docker-monitoring/</link><pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/solutions/technologies/docker-monitoring/</guid><description>Netdata brings the simplicity Docker promised to monitoring. One command install, instant visibility into every container&amp;rsquo;s CPU, memory, disk, and network. No agents per container, no complex pipelines, no surprise bills.</description></item><item><title>Linux Load Average Myths and Realities</title><link>https://www.netdata.cloud/blog/linux-load-average-myths-and-realities/</link><pubDate>Sun, 03 Nov 2024 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/linux-load-average-myths-and-realities/</guid><description>&lt;p>When it comes to monitoring system &lt;a href="https://www.netdata.cloud/solutions/technologies/linux-monitoring/">performance on Linux&lt;/a>, the load average is one of the most referenced metrics. Displayed prominently in tools like &lt;code>top&lt;/code>, &lt;code>uptime&lt;/code>, and &lt;code>htop&lt;/code>, it&amp;rsquo;s often used as a quick gauge of system load and capacity. But how reliable is it? For complex, multi-threaded applications, load average can paint a misleading picture of actual system performance.&lt;/p>
&lt;p>In this article, we&amp;rsquo;ll dive into the myths and realities of Linux load average, using insights from Netdata’s high-frequency, high-concurrency monitoring setup. Through this journey, we&amp;rsquo;ll uncover why load average spikes can occur even under steady workloads, and why a single metric is rarely enough to capture the true state of a system. Whether you&amp;rsquo;re a system administrator, developer, or performance enthusiast, this exploration of load average will help you interpret it more accurately and understand when it may—or may not—reflect reality.&lt;/p></description></item><item><title>Understanding Interrupts, Softirqs, and Softnet in Linux</title><link>https://www.netdata.cloud/blog/understanding-interrupts-softirqs-and-softnet-in-linux/</link><pubDate>Tue, 02 May 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/understanding-interrupts-softirqs-and-softnet-in-linux/</guid><description>&lt;p>&lt;img src="../2023-05-02-understanding-interrupts-softirqs-and-softnet-in-linux/img/stacked-netdata.png" alt="stacked-netdata">&lt;/p>
&lt;p>Interrupts, softirqs, and softnet are all critical parts of the Linux kernel that can impact system performance. In this blog post, we&amp;rsquo;ll explore their usefulness, and discuss how to monitor them using Netdata for both bare-metal servers and VMs.&lt;/p>
&lt;!-- truncate -->
&lt;h2 id="what-are-interrupts">What are Interrupts?&lt;/h2>
&lt;p>Interrupts are signals generated by hardware devices to indicate that they require attention from the CPU. Hardware devices can generate interrupts for a variety of reasons, including data transmission or reception, input/output operations, and other activities. When an interrupt is generated, the CPU stops what it is doing and handles the interrupt. Interrupts can have a significant impact on system performance, especially if there are a high number of interrupts occurring.&lt;/p></description></item><item><title>Understanding System Processes States</title><link>https://www.netdata.cloud/blog/understanding-system-processes-states/</link><pubDate>Tue, 02 May 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/understanding-system-processes-states/</guid><description>&lt;p>&lt;img src="../2023-05-02-understanding-system-processes-states/img/stacked-netdata.png" alt="stacked-netdata">&lt;/p>
&lt;p>The different states of system processes are essential to understanding how a computer system works. Each state represents a specific point in a process&amp;rsquo;s life cycle and can impact system performance and stability.&lt;/p>
&lt;!-- truncate -->
&lt;h2 id="process-states">Process States&lt;/h2>
&lt;p>Netdata&amp;rsquo;s &lt;code>system.processes_state&lt;/code> chart provides a view of these states, allowing users to monitor system performance in real-time:&lt;/p>
&lt;p>&lt;img src="../2023-05-02-understanding-system-processes-states/img/system-processes.png" alt="system-processes">&lt;/p>
&lt;ol>
&lt;li>
&lt;p>&lt;strong>Running:&lt;/strong> A process is in the Running state when it is actively using the CPU and executing instructions. This state is resource-intensive and can lead to performance issues if there are too many Running processes, causing CPU contention and system slowdowns. Processes in the Running state are prioritized using scheduling algorithms to improve system performance.&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>Monitor KSM performance with Netdata</title><link>https://www.netdata.cloud/blog/ksm/</link><pubDate>Tue, 01 Nov 2022 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/ksm/</guid><description>&lt;p>Monitoring KSM (Kernel Same-page Merging) performance at deduping memory shared across VMs.&lt;/p>
&lt;!--truncate-->
&lt;h2 id="kernel-same-page-merging-ksm">Kernel Same-page Merging (KSM)&lt;/h2>
&lt;p>Linux kernels store memory in &lt;strong>pages&lt;/strong> which are moved in and out of memory as a single block. On most Linux architectures pages are 4096 bytes. &lt;strong>KSM&lt;/strong> (Kernel Same-page Merging) is a kernel feature that scans memory looking for pages with identical content, and then de-duplicates them. The most common use-case where such duplicate pages occur is on hosts running multiple virtual machines (VMs).&lt;/p></description></item></channel></rss>