<?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/e3abfaf22eca4fd9a6eb01fcace20b6f&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/e3abfaf22eca4fd9a6eb01fcace20b6f-a9e728c84b88af7b.gif</thumbnail_url><duration>99.866667</duration><title>Using FullStory Dashboard for Bug Triage</title><description>This quarter I focused on bug squashing and used FullStory dashboards to quickly find where issues are happening. I started with the issue monitoring dashboard, where FullStory pre tools key metrics like dead clicks and rage clicks. I noticed a big spike in rage clicks on the products and search page, and a similarly timed spike on the word checkout. I then went back to uncaught exception errors and dimensionized the metric by text for a 30 day period to see specifics. I exported a PNG for internal communications. No viewer action was requested.</description></oembed>