<?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/bb41691598dc4aedb5cd083d18e29bc3&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/bb41691598dc4aedb5cd083d18e29bc3-8c94f0c040d8d81c.gif</thumbnail_url><duration>126.333</duration><title>Proactive Full Story Alerts with Metrics 🚨</title><description>I walked through how to be proactive in FullStory by turning an event trend into a metric, then creating an alert with daily or other thresholds and options like relative or absolute change. I can choose when to be alerted as the value crosses a threshold or on every day it repeats, and route alerts via in app notifications, email, or Slack. I shared examples like triggering support desk ticket creation when daily volume exceeds expected norms. I also use watched in app error toast trends to anticipate service disruptions before they become widespread. No action was explicitly requested from viewers.</description></oembed>