<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident-Response on Home</title><link>https://bala-krishnan.com/tags/incident-response/</link><description>Recent content in Incident-Response on Home</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bala-krishnan.com/tags/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>Lamplighter - One Timeline for Every Log</title><link>https://bala-krishnan.com/posts/26-lamplighter/</link><pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate><guid>https://bala-krishnan.com/posts/26-lamplighter/</guid><description>When something breaks in production, the first ten minutes usually look the same. One terminal tailing the API pod. Another tailing the worker. A third running kubectl get events -w. Maybe a fourth on the ingress controller, if you can remember which namespace it lives in and what its labels are. Then you start flipping between them, trying to work out what happened first.
That last part is the actual job, and none of the tools help with it.</description></item></channel></rss>