Dogfooding Chronicles
Dogfooding Chronicles is a series in which we gaze upon our navels and share tales of how we fix our product using our product.
Replaying Backend Errors using Sentry’s Session Replay
Dogfooding ChroniclesWith Session Replay tools, you can more easily see what user actions lead to an error. For example, Sentry’s Session Replay is a first class…
Read onDogfooding Chronicles: Weekly Report Emails
Dogfooding ChroniclesIf 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…
Read onMaking a Time Zone Picker Control for .NET MAUI
Dogfooding ChroniclesIn this post, Matt-Johnson Pint from the Sentry .NET team walks us through how he made a Time Zone Picker user interface control for .NET MAUI, leveraging MAUI's support for platform-specific code.
Read onMonitoring our Local Development Environment with Sentry
Dogfooding ChroniclesIs 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.
Read onInstrumenting Our Frontend Test Suite (...and fixing what we found)
Dogfooding ChroniclesAdding Instrumentation to Jest Here at Sentry, we like to dogfood our product as much as possible. Sometimes, it results in unusual…
Read onDogfooding Chronicles: Never Be Content With Your Content (Security Policies)
Dogfooding ChroniclesA 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.
Read onUsing Sentry Performance To Make Sentry Performant
Dogfooding ChroniclesLike many companies, Sentry uses feature flags to determine when certain users see certain features. Recently, we decided to switch our…
Read onIssue Detail Performance Improvements
Dogfooding ChroniclesOne 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…
Read onPatching A Flood of 404s
Dogfooding ChroniclesIn our latest edition of Dogfooding Chronicles, we use Discover to root out the bane of all companies everywhere: the 404 page.
Read onVerifying Large Refactors in Production with Sentry
Dogfooding ChroniclesRecently we used Sentry to ensure we didn’t break Sentry while doing a large code refactoring project.
Read onFinding and Fixing Django N+1 Problems
Dogfooding ChroniclesSentry now detects N+1 issues. Learn more about how to find and fix Django N+1 problems here.
Read onGo-Getting Lazy-Loading
Dogfooding ChroniclesIn our latest edition of the Dogfooding Chronicles, we use Performance to motivate lazy-loading user-facing data.
Read onHandling GraphQL Errors Using Sentry
Dogfooding ChroniclesWhen GraphQL queries go wrong, the focus is usually on handling the returned exception. Learn how to take the original GraphQL request & translate it into a more informative response with Sentry.
Read onDogfooding Chronicles: Thinking Backward, Moving Forward
Dogfooding ChroniclesIn 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.
Read onDogfooding Chronicles: Tracing the path from “It’s Slow” to “What’s Slow”
Dogfooding ChroniclesIn 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.
Read onFixing Sentry with Sentry: Lock-Contention Edition
Dogfooding ChroniclesWe recently experienced two minor outages (sorry about that). Here's how we found and fixed the issue.
Read onCapture Content Security Policy (CSP) Violations with Sentry
Dogfooding ChroniclesA closer look at how you can use Sentry to easily capture CSP violations.
Read onA peek at your privacy
Here’s a quick look at how Sentry handles your personal information (PII).
×Who we collect PII from
We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
Am I included?PII we may collect about you
- PII provided by you and related to your
- Account, profile, and login
- Requests and inquiries
- Purchases
- PII collected from your device and usage
- PII collected from third parties (e.g., social media)
How we use your PII
- To operate our site and service
- To protect and improve our site and service
- To provide customer care and support
- To communicate with you
- For other purposes (that we inform you of at collection)
Third parties who receive your PII
We may disclose your PII to the following type of recipients:
- Subsidiaries and other affiliates
- Service providers
- Partners (go-to-market, analytics)
- Third-party platforms (when you connect them to our service)
- Governmental authorities (where necessary)
- An actual or potential buyer
We use cookies (but not for advertising)
- We do not use advertising or targeting cookies
- We use necessary cookies to run and improve our site and service
- You can disable cookies but this can impact your use or access to certain parts of our site and service
Know your rights
You may have the following rights related to your PII:
- Access, correct, and update
- Object to or restrict processing
- Port over
- Opt-out of marketing
- Be forgotten by Sentry
- Withdraw your consent
- Complain about us
If you have any questions or concerns about your privacy at Sentry, please email us at compliance@sentry.io.
If you are a California resident, see our Supplemental notice.