{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/e3abfaf22eca4fd9a6eb01fcace20b6f\" 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/e3abfaf22eca4fd9a6eb01fcace20b6f-a9e728c84b88af7b.gif","duration":99.866667,"title":"Using FullStory Dashboard for Bug Triage","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."}