<?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 Tokenise</title><link>https://tokenise.rosvetic.com/tags/incident-response/</link><description>Recent content in Incident-Response on Tokenise</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Tue, 13 Oct 2026 07:03:00 +0000</lastBuildDate><atom:link href="https://tokenise.rosvetic.com/tags/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>Turn a failing deploy log into a draft incident timeline in one command</title><link>https://tokenise.rosvetic.com/posts/incident-draft-from-ci-log/</link><pubDate>Tue, 13 Oct 2026 07:03:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/incident-draft-from-ci-log/</guid><description>&lt;p&gt;It&amp;rsquo;s 3:40pm, the error-rate alert has been quiet for nine minutes, and someone has to write the incident summary before everyone forgets what happened. The raw material is a deploy log, three alert lines, a pager acknowledgement and a git history nobody has looked at since the rollback. Assembling that into a timeline is forty minutes of copy and paste, and it&amp;rsquo;s done by the person who is most tired.&lt;/p&gt;</description></item></channel></rss>