From dd80f221ad19213b7debe867db4d790bddaa89e2 Mon Sep 17 00:00:00 2001 From: Alex Krawiec Date: Mon, 4 Aug 2025 15:17:03 -0700 Subject: [PATCH 1/2] First draft of em concept page --- docs/concepts/key-terms/error-monitoring.mdx | 66 ++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 docs/concepts/key-terms/error-monitoring.mdx diff --git a/docs/concepts/key-terms/error-monitoring.mdx b/docs/concepts/key-terms/error-monitoring.mdx new file mode 100644 index 00000000000000..2c2025ea51528d --- /dev/null +++ b/docs/concepts/key-terms/error-monitoring.mdx @@ -0,0 +1,66 @@ +--- +title: What Is Error Monitoring? +sidebar_order: 20 +description: Learn how error monitoring works, why it matters, and how Sentry helps track and fix bugs in real time. +--- + + +# What is Error Monitoring? + +Error monitoring is your app's always-on debugger. It tracks crashes, exceptions, and runtime issues as they happenā€”complete with stack traces, request data, environment details, and user context. That means you can spot patterns, prioritize what matters, and fix bugs fast (before your users even file a ticket). Think of error monitoring as a babysitter for your code, but one that actually tells you *why* the baby's crying. + +## Why Error Monitoring Matters + +Modern apps have a lot going on: different browsers, devices, APIs, cloud services... it's basically a tech jungle out there. Without proper error monitoring, bugs can sneak around unnoticed until users start bumping into them (and filing angry support tickets). That's where error monitoring comes in. It helps teams: + +- šŸž **Catch issues early**, before they snowball into full-blown outages. +- šŸ” **Trace bugs to their source** with rich, developer-friendly diagnostics. +- šŸ”§ **Boost stability** by staying ahead of problemsā€”not just reacting to them. +- šŸŽÆ **Keep users happy** by smoothing out those rough edges before they feel them. + +## Key Features of an Error Monitoring System + +A great error monitoring tool doesn't just spot bugsā€”it rolls up its sleeves and helps you squash them. Here's what to look for: + +- **Automatic Error Detection** + Think of error detection as a bug-sniffing dog. It catches uncaught exceptions, failed network calls, performance hiccups across both front-end and back-end. + +- **Real-Time Alerts** + The moment something breaks, you'll know. Whether it's via Slack, email, PagerDuty, or a smoke signal (okay, maybe not that), you'll get notified fast. + +- **Detailed Error Reports** + No more vague ā€œsomething went wrongā€ messages. You'll get stack traces, user info, environment details, release data, and even breadcrumbs showing exactly what led up to the bug. + +- **Issue Grouping and Deduplication** + Keeps your inbox (and your brain) from overflowing by bundling similar errors together. One alert for one issueā€”no duplicates, no noise. + +- **Integrations with Your Dev Toolkit** + Hooks right into tools like GitHub, Jira, and CI/CD pipelines so you can trace bugs to the commit that caused them and spin up a fix without leaving your flow. + +## Common Use Cases for Error Monitoring + +- Monitoring JavaScript errors in web applications +- Detecting backend exceptions in Node.js, Python, Ruby, Java, or Go services +- Tracking mobile app crashes on iOS and Android +- Logging failed API calls and latency spikes in microservices +- Catching errors during user interactions or checkout flows + +## The Error Monitoring Workflow + +1. **Install a lightweight SDK** - Set it up once, and boom: your app now has x-ray vision. +2. **Let the errors roll in** - It'll auto-catch most issues, but you can log your own too (because you're thorough like that). +3. **Send error data** to your monitoring platform, complete with stack traces and context. +4. **Get pinged instantly** - Slack, email, carrier pigeonā€”whatever works. You'll know the moment something breaks. +5. **Fix it like a hero** - Triage, dig into the details, squash the bug, and ship with confidence. + +## Who's Using Error Monitoring? + +- **Developers**, to catch bugs in the act, trace them back to the source, and fix things *before* users start tweeting. +- **QA teams**, to double-check that fixes actually fixed stuff, and keep regressions from crashing the party. +- **Product teams**, to see how bugs impact real users, prioritize what matters, and keep the roadmap bug-free(ish). +- **SREs**, to keep the app running smoothly, spot weird spikes, and sleep better knowing nothing's secretly on fire. +- **New devs & code-curious humans** - to see what broke, why it broke, and become a better coder in the process. + +## Sentry's Error Monitoring Offering + +We're admittedly partial to [Sentry's Error Monitoring](/product/#error-monitoring), and for good reason. With real-time alerts, automatic error grouping, and actionable insights, the [Issues Page](/product/issues/) makes it easy to track and understand every bug in your code. Sentry offers SDKs for nearly every major platform, so setup is simple. You can also enhance your monitoring by adding products like [Tracing](/concepts/key-terms/tracing/), [Replays](/product/explore/session-replay/), [Prevent](/product/ai-in-sentry/sentry-prevent-ai/), and [Seer](/product/ai-in-sentry/seer/), giving you end-to-end visibility into your application's behavior. \ No newline at end of file From 1edc767b722a2cfed52430cea842a0720117db54 Mon Sep 17 00:00:00 2001 From: Alex Krawiec Date: Mon, 4 Aug 2025 15:39:46 -0700 Subject: [PATCH 2/2] Remove double title --- docs/concepts/key-terms/error-monitoring.mdx | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/concepts/key-terms/error-monitoring.mdx b/docs/concepts/key-terms/error-monitoring.mdx index 2c2025ea51528d..110004efffc805 100644 --- a/docs/concepts/key-terms/error-monitoring.mdx +++ b/docs/concepts/key-terms/error-monitoring.mdx @@ -4,9 +4,6 @@ sidebar_order: 20 description: Learn how error monitoring works, why it matters, and how Sentry helps track and fix bugs in real time. --- - -# What is Error Monitoring? - Error monitoring is your app's always-on debugger. It tracks crashes, exceptions, and runtime issues as they happenā€”complete with stack traces, request data, environment details, and user context. That means you can spot patterns, prioritize what matters, and fix bugs fast (before your users even file a ticket). Think of error monitoring as a babysitter for your code, but one that actually tells you *why* the baby's crying. ## Why Error Monitoring Matters