<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident-Detection on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/incident-detection/</link><description>Recent content in Incident-Detection on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 30 Sep 2026 16:35:00 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/incident-detection/index.xml" rel="self" type="application/rss+xml"/><item><title>Incident detection rebuilt on OTel, Kafka, and Flink: 40s→10s</title><link>https://curadevops.metacog.co.kr/insights/2026-09-30-from-40-seconds-to-under-10-rebuilding-incident-detection-on/</link><pubDate>Wed, 30 Sep 2026 16:35:00 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-30-from-40-seconds-to-under-10-rebuilding-incident-detection-on/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> A practical case study on reducing incident detection latency using OpenTelemetry, Kafka, and Flink on Kubernetes — useful for teams evaluating or redesigning their observability pipeline architecture, but no deployment action required.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A concrete example of platform investment paying off in reliability metrics; useful context for framing observability stack decisions but no strategic action required.&lt;/li>
&lt;/ul></description></item></channel></rss>