Operations | Monitoring | ITSM | DevOps | Cloud

TrackJS

Powerful Ignore Rules for Noisy JavaScript Errors

Ignoring noisy and external errors is important to understanding the health of your client-side applications. Third-party scripts, user extensions, content crawlers, and non-impactful errors create lots of noise in web operations. With TrackJS Ignore Rules, you can filter out this noise and and have a clear view of your web application quality.

A Dumpster-Fire Alert for Your JavaScript Errors

Do you work with an app that’s a dumpster-fire of errors? Wishing for an appropriate alert when you need to fight down the flames? Look no further friend. Today, we’re creating a Dumpster fire notification for your JavaScript errors with Particle and TrackJS. My friend Kristina is a wizard with hardware and LEDs. Awhile back, she made the dumpster fire to present at a conference, and she printed an extra one for me!

The Ongoing State of JavaScript Errors

Today, we’re releasing TrackJS Global Error Statistics to the public. This aggregated production data is a useful measure of the state of client-side JavaScript errors and the quality of the web. We break it down by the most common errors, browsers, and operating systems. We did this a few years ago with the State of Client-Side JavaScript Errors. It was quite useful, but very time consuming to produce.

What is Developer Time Worth?

It’s remarkable to me how many developers have no idea what their time is worth. I speak with a lot of developers, and when I mention my work on TrackJS, I frequently hear “I could build that”. Yeah, you could. Observability tools aren’t rocket science. But you shouldn’t. Your time is too valuable to build better mousetraps. Your time is valuable and finite. Both to you and to your company.