<?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>Origin Pull on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/origin-pull/</link><description>Recent content in Origin Pull 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>Thu, 24 Sep 2026 00:33:21 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/origin-pull/index.xml" rel="self" type="application/rss+xml"/><item><title>Cache Hit Rate from 58% to 94%: Building a CDN Monitoring System and 5 Production-Grade Troubleshooting Decisions</title><link>https://www.sre.wang/en/posts/monitoring-cdn-edge-monitoring/</link><pubDate>Thu, 24 Sep 2026 00:33:21 +0800</pubDate><guid>https://www.sre.wang/en/posts/monitoring-cdn-edge-monitoring/</guid><description>CDN monitoring is not just about checking a hit rate number. This article breaks down a production-grade CDN monitoring system across three dimensions: cache hit rate, origin bandwidth, and edge node health, covering Prometheus collection, Grafana dashboard design, alert rules, and 5 real troubleshooting cases.</description></item></channel></rss>