{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/d21d2cf8dfa447bc8d8fa9ca5ea2ef39\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/d21d2cf8dfa447bc8d8fa9ca5ea2ef39-b142fde0897ae717.gif","duration":269.312,"title":"Holmes Triage and Root Cause in Slack","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."}