<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Misconfigured-Alerts on Netdata</title><link>https://www.netdata.cloud/tags/misconfigured-alerts/</link><description>Recent content in Misconfigured-Alerts on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/misconfigured-alerts/index.xml" rel="self" type="application/rss+xml"/><item><title>Misconfigured Alert Detection: Tuning Made Easy</title><link>https://www.netdata.cloud/blog/identifying-misconfigured-alerts/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/identifying-misconfigured-alerts/</guid><description>&lt;p>&lt;img src="../images/miscon-alerts-1.png" alt="Misconfigured Alert Detection: Find the Alerts That Need Tuning">&lt;/p>
&lt;p>Netdata ships with hundreds of stock alerts. They cover a wide range of infrastructure conditions and they&amp;rsquo;re designed with sensible defaults. But &amp;ldquo;sensible defaults&amp;rdquo; and &amp;ldquo;correct for your environment&amp;rdquo; are not the same thing. A CPU threshold that&amp;rsquo;s perfectly reasonable for a build server might generate constant noise on a machine running batch jobs. An alert that&amp;rsquo;s critical for production might be irrelevant in staging, where it fires daily and everyone ignores it.&lt;/p></description></item></channel></rss>