Sentry for Breakpad
Your apps are crashing everywhere, but you can easily capture all that crash data thanks to the magic of Breakpad.
Getting Started is Simple
Conceived initially by Microsoft for crash reports on Windows, minidumps have become an accessible format for all sorts of native crashes. You can generate and upload minidumps yourself using Breakpad, use a higher-level SDK for platforms with built-in support for native crashes like Cocoa or Electron, and use them to triage issues with C++.
Check our documentation for the latest instructions.
See all platformsStop Guessing
Collect native crash events in your issue stream, grouped by their crash location. See detailed stack traces with resolved function names, file location, and CPU register values. Assign issues to the engineers — or teams — who wrote the code that broke everything. (Obviously that would never, ever be you.)
See The Big Picture
Event trails detail what the app was doing before any error occurred. Is the problem actually outside of your code? Was it caused by something another team wrote that broke the API you’re using? Sentry can tell you that too.
No WiFi? No Problem.
Record events even when devices are offline or in airplane mode, then send errors as soon as connection is regained.
“We reduced false alerts by more than 50% by fine tuning the thresholds and defining the criteria that works best for us with Sentry alerts-it's a completely new world for monday.com.”
Bugs are dumb. You probably aren’t.
Record environment and state details so you can recreate bugs, whether you’re targeting Windows, macOS, Linux, iOS, or Android.
Use Sentry’s tag distribution graph to isolate and prioritize any error by seeing how often it occurs in context.
Find answers to key questions: How actionable is the error? Can I just ignore it?