<?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 TCS Labs Academy</title><link>https://meshery-extensions.github.io/tcslabs-academy/pr-preview/pr-36/tags/incident-response/</link><description>Recent content in Incident-Response on TCS Labs Academy</description><generator>Hugo</generator><language>en</language><atom:link href="https://meshery-extensions.github.io/tcslabs-academy/pr-preview/pr-36/tags/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>Respond</title><link>https://meshery-extensions.github.io/tcslabs-academy/pr-preview/pr-36/learning-paths/deea6061-b6be-49a9-ad1c-f1a5c32e1fa9/coding-agents-for-cloud-native-operations/incident-response-with-coding-agents/respond/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://meshery-extensions.github.io/tcslabs-academy/pr-preview/pr-36/learning-paths/deea6061-b6be-49a9-ad1c-f1a5c32e1fa9/coding-agents-for-cloud-native-operations/incident-response-with-coding-agents/respond/</guid><description/></item><item><title>2. Incident Response with Coding Agents</title><link>https://meshery-extensions.github.io/tcslabs-academy/pr-preview/pr-36/learning-paths/deea6061-b6be-49a9-ad1c-f1a5c32e1fa9/coding-agents-for-cloud-native-operations/incident-response-with-coding-agents/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://meshery-extensions.github.io/tcslabs-academy/pr-preview/pr-36/learning-paths/deea6061-b6be-49a9-ad1c-f1a5c32e1fa9/coding-agents-for-cloud-native-operations/incident-response-with-coding-agents/</guid><description>&lt;p&gt;Incidents do not wait for business hours, and human responders cannot simultaneously gather telemetry, search runbooks, and coordinate remediation without dropping context. Coding agents can close that gap - not by replacing the on-call engineer, but by compressing the time between alert and diagnosis.&lt;/p&gt;
&lt;p&gt;This course walks through the full incident lifecycle: detecting and triaging a failure, executing structured runbooks with agent assistance, working through a realistic crashloop recovery, and then using an LLM to draft a blameless postmortem from the incident timeline. Each lesson is grounded in real Meshery and Kubernetes tooling, with explicit checkpoints for human review and approval.&lt;/p&gt;</description></item></channel></rss>