<?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>Memory Monitoring on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/memory-monitoring/</link><description>Recent content in Memory Monitoring 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, 09 Oct 2026 09:47:51 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/memory-monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Pods OOM Killed at 3 AM: From working_set Blind Spots to a Memory Warning System in 5 Production Decisions</title><link>https://www.sre.wang/en/posts/monitoring-container-memory-oom-warning/</link><pubDate>Fri, 09 Oct 2026 09:47:51 +0800</pubDate><guid>https://www.sre.wang/en/posts/monitoring-container-memory-oom-warning/</guid><description>Pods get OOMKilled while monitoring shows 20% memory left? Demystify the four cAdvisor memory metric blind spots, 5 production-level warning decisions (compound alerts, CPU throttle correlation, trend detection) with complete PromQL configs that raised OOM alert accuracy from 60% to 95%</description></item></channel></rss>