<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/d21d2cf8dfa447bc8d8fa9ca5ea2ef39&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/d21d2cf8dfa447bc8d8fa9ca5ea2ef39-b142fde0897ae717.gif</thumbnail_url><duration>269.312</duration><title>Holmes Triage and Root Cause in Slack</title><description>This Loom demonstrates how HOMS, the ARS-RE agent, connects to Incident.io to triage and automatically diagnose a live alert before humans take over. The presenter triggers a Grafana alert that a sound deployment is broken due to database connectivity issues, and HOMS joins a dedicated Slack channel to investigate by running kubectl commands in the Kubernetes cluster. The incident status changes from triage to major, and the automated root cause analysis reports a crash loop tied to a misconfigured environment variable with the wrong database name. A shortened Slack update then summarizes the incident as ready for human review with the identified cause.</description></oembed>