<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Netdata - vo.rs</title><link>https://vo.rs/tags/netdata/</link><description>Latest from the Netdata desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 11 Jul 2024 15:55:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/netdata/" rel="self" type="application/rss+xml"/><item><title>Netdata in an Afternoon: Per-Second Metrics, Zero Config</title><link>https://vo.rs/story/netdata-in-an-afternoon-per-second-metrics-zero-config/</link><description>&lt;p&gt;Most monitoring setups sample every fifteen seconds. Prometheus defaults to it, and for a great many things fifteen seconds is fine. Then one day a service stutters — a CPU spike that lasts four seconds, a disk that saturates for a moment, a burst of network that fills a buffer — and your fifteen-second dashboard shows a serene flat line, because the event began and ended entirely between two samples. You know something happened. You have no picture of it. The resolution ate the evidence.&lt;/p&gt;</description><pubDate>Thu, 11 Jul 2024 15:55:00 +0000</pubDate></item></channel></rss>