<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Prometheus on Besterry — Linux &amp; DevOps Notes</title><link>https://besterry.com/tags/prometheus/</link><description>Recent content in Prometheus on Besterry — Linux &amp; DevOps Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 10 Jun 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://besterry.com/tags/prometheus/index.xml" rel="self" type="application/rss+xml"/><item><title>Alert Fatigue: Prometheus Rules That Actually Help</title><link>https://besterry.com/posts/prometheus-alerts/</link><pubDate>Mon, 10 Jun 2024 00:00:00 +0000</pubDate><guid>https://besterry.com/posts/prometheus-alerts/</guid><description>&lt;p&gt;Most alerts are noise. The hardest part of monitoring is deciding what NOT to alert on. Here is the framework I use.&lt;/p&gt;
&lt;h2 id="rule-1-every-alert-must-be-actionable"&gt;Rule 1: Every alert must be actionable&lt;/h2&gt;
&lt;p&gt;If you get paged and there is nothing to do, the alert should not exist. Either fix the root cause, automate the response, or let it be a metric trend instead of a page.&lt;/p&gt;
&lt;h2 id="rule-2-alert-on-user-visible-symptoms"&gt;Rule 2: Alert on user-visible symptoms&lt;/h2&gt;
&lt;p&gt;Instead of HighCPUUsage, prefer HighRequestLatency. CPU usage high with good latency means the system is working as designed. Latency high means users are hurting.&lt;/p&gt;</description></item></channel></rss>