<?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/2dacf0cb10484ed7844da2ebb55a171e&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/2dacf0cb10484ed7844da2ebb55a171e-73ac8835362570e4.gif</thumbnail_url><duration>63.631</duration><title>Billsnap Detects Unusual GCP Billing Spikes</title><description>This Loom introduces BillSnap to catch unusual GCP spending that native budget alerts miss. The author explains that built-in alerts only trigger at fixed dollar thresholds, and cites a real incident where a Dataflow job leaked $1800 over a weekend before the alert fired. BillSnap connects a project and, every morning, pulls the billing export and computes a 14-day rolling baseline per SKU. It then flags spending that exceeds two standard deviations from that baseline.</description></oembed>