<?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>Alert Noise on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/alert-noise/</link><description>Recent content in Alert Noise on SRE Engineering Practice</description><image><title>SRE Engineering Practice</title><url>https://www.sre.wang/share-card-square.jpg</url><link>https://www.sre.wang/share-card-square.jpg</link></image><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 30 Oct 2026 00:40:16 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/alert-noise/index.xml" rel="self" type="application/rss+xml"/><item><title>One Error Log Pinged Me 400 Times: Two-Tier Log Alerting That Tells 'It Happened' Apart From 'It Is Happening'</title><link>https://www.sre.wang/en/posts/loki-log-based-alerting-rules/</link><pubDate>Fri, 30 Oct 2026 00:40:16 +0800</pubDate><guid>https://www.sre.wang/en/posts/loki-log-based-alerting-rules/</guid><description>Log alerting spams because it treats &amp;#39;this appeared in the logs&amp;#39; as &amp;#39;this is broken right now.&amp;#39; Using a real incident that fired 400+ notifications in ten minutes, this article walks through a two-tier fix: recording rules first compress the event stream into state metrics, then alert rules fire only when that state persists. Includes a complete Loki ruler configuration, copy-ready rule files, label convergence thresholds, and the four production traps — silent WAL replay, random re-sharding, no globs on local storage, and inconsistent local rule evaluation.</description></item></channel></rss>