Dashboarding Our Way to the Future

on YouTube ↗19m

" summary

Node plus a small tool kit (Glitch, GitHub, Heroku) produces a working triage dashboard that keeps daily snapshots of Bugzilla data, fetching once a day at 6:00 a.m., surviving the 10,000‑bug API limit, and avoiding custom servers. It handles 127 new bugs a day (≈5,334 per six‑week cycle), moves from static page to an Express app, exports via Glitch → GitHub → Heroku flow, and proved useful enough to help ship Firefox Quantum as a real, maintained dashboard.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 3:31What Does a Bug Lifecycle Look like in Bugzilla
3. 4:17Bugzilla
4. 8:25What's Glitch
5. 16:59Predicting if a Bug Is a Regression
6. 17:47Closing

" related talks

• 39mCreating a realtime dashboard with PHP and websocketsFreek van der Herten · Dutch PHP Conference 2017
• 25mMy node.js process is on fireMatteo Collina · jsDay 2018
• 33mWork Less and Do More: Sheets for Node.js DevelopersFranziska Hinkelmann, Anu Srivastava · Google I/O 2019
• 08mMonitoring Errors and Slowdowns with a JS Frontend and Node BackendChris Stavitsky · Node Congress 2022
• 17mLogging, Metrics, and Tracing with Node.jsThomas Hunter II · Node Congress 2021
• 26mObserving Node.js: Using Metrics to Improve your Application PerformanceGuilherme Hermeto · OpenJS World 2021
• 22mNode.js at UBERJake Verbaten · NodeConf EU 2014
• 26mMonitoring Node.js Microservices on CloudFoundry with Open Source Tools and a Shoestring BudgetTony Erwin · Cloud Foundry Summit Silicon Valley 2017