<?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/b63f0eba0fd74750929f37c16b3fca3b&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/b63f0eba0fd74750929f37c16b3fca3b-a257f59db2189043.gif</thumbnail_url><duration>119.4135</duration><title>HolmesGPT - &amp;quot;What Happened Here?&amp;quot;</title><description>In this video, I showcase the incredible capabilities of Holmes GPT when analyzing CPU usage spikes in my cluster, specifically focusing on Prometheus. I demonstrate how Holmes can visually interpret graphs and gather relevant data, such as application logs and Kubernetes events, to provide a comprehensive understanding of what happened at the time of the spike. I discovered that the CPU spike was due to Prometheus performing database compaction, which is a periodic process that causes significant resource usage. I encourage you to explore how Holmes can enhance your monitoring and troubleshooting efforts. Please let me know if you have any questions or need further insights!</description></oembed>