Dogfooding Chronicles

If you’re a Sentry user, you’ve probably seen those weekly emails we send out at the start of the week. They give a weekly recap to users of…

Is your organization's local development environment plagued with issues? Read on how you can use Sentry to monitor it and help you solve issues quickly.

Adding Instrumentation to Jest Here at Sentry, we like to dogfood our product as much as possible. Sometimes, it results in unusual…

A Content Security Policy (CSP) lets a browser know which content sources are to be trusted — and which aren’t. Learn how to update your CSP and protect your application.

Like many companies, Sentry uses feature flags to determine when certain users see certain features. Recently, we decided to switch our…

One of Sentry’s most-trafficked pages is our issue details page, as it helps our customers understand the root cause of an error. For those…

In our latest edition of Dogfooding Chronicles, we use Discover to root out the bane of all companies everywhere: the 404 page.

Recently we used Sentry to ensure we didn’t break Sentry while doing a large code refactoring project.

Sentry now detects N+1 issues. Learn more. The Django Python framework allows people to build websites extremely fast. One of its best…

In our latest edition of the Dogfooding Chronicles, we use Performance to motivate lazy-loading user-facing data.

When GraphQL queries go wrong, the focus is usually on handling the returned exception. Guest contributor, Bruno Scheufler, writes about how he takes the original GraphQL request and translates it into a more informative response, using Sentry

In part two of Dogfooding Chronicles, our team used all available resources — Discover, Metric Alerts, and our new Performance offering — to track a slow-loading frontend issue back to its backend origins.

In part one of Sentry’s Dogfooding Chronicles, find out how we used Performance’s application monitoring features to keep a slow product demo from demoralizing the team.

We recently experienced two minor outages (sorry about that). Here's how we found and fixed the issue.

A closer look at how you can use Sentry to easily capture CSP violations.