<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alerting on Netdata</title><link>https://www.netdata.cloud/tags/alerting/</link><description>Recent content in Alerting on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 30 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/alerting/index.xml" rel="self" type="application/rss+xml"/><item><title>How To Reduce Alert Fatigue With Anomaly Detection</title><link>https://www.netdata.cloud/solutions/use-cases/alert-fatigue/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/solutions/use-cases/alert-fatigue/</guid><description>Most alert-fatigue tools manage noise after the fact. Netdata prevents it by running 18 ML models per metric with consensus voting — anomalies only fire when multiple models agree, suppressing the false positives that drive on-call burnout.</description></item><item><title>Text-To-Alert: Create Alerts From Natural Language</title><link>https://www.netdata.cloud/blog/ai-alerts/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/ai-alerts/</guid><description>&lt;p>Netdata has an incredibly powerful alerting engine. But this can sometimes be a double-edged sword: the flexibility to build incredibly specific, intelligent alerts is immense, but mastering its syntax can feel like learning a new language. We’ve heard this from so many of you. You tell us that configuring alerts is often the steepest part of the learning curve, a task that falls to the one &amp;ldquo;Netdata expert&amp;rdquo; on the team who has spent the time digging through the documentation.&lt;/p></description></item></channel></rss>