Recently, we ran into a scary looking error message in the Chrome console, Refused to get unsafe header "TrackJS-Correlation-Id". Our code was indeed trying to read this header from a request, so we explored this right away. The funny thing is, other than the error message in Chrome, everything was working fine.

The TrackJS team is hard at work streamlining the system and giving you even better tools to capture, understand, and fix the errors on the web. Here’s what we’ve been up to lately:

The web is full of ads, and many users install ad blocker extensions to deal with them. But ad blocker extensions can break websites in strange and unintended ways, which often show up as errors in TrackJS.

Ad blocker-related errors are common across our customers. So after debugging a few ad blocker-related issues myself recently, I thought I’d share 3 Tips to Avoid Ad Blocker Errors.

Is that click-bait-y enough?

Your monitoring, instrumentation, and observability systems should be separated from your primary system infrastructure for resiliency and visibility. You already know monitoring is important, but you should also consider where you host your monitoring, to understand real user experience and recover from outages quickly.

A fictional story about software development.

Sarah pulled up her LogCorp dashboard to start debugging. Customers were having sporadic issues checking out from the Acme site, but no one knew why. “This logging tool is so complex” she thought, “I have to re-learn this stupid query language every time.”

The TrackJS team is hard at work streamlining the system and giving you even better tools to capture, understand, and fix the errors on the web. Here’s what we’ve been up to lately: