First draft of em concept page #14547
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Bundle ReportChanges will increase total bundle size by 1.58kB (0.01%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
| 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. |
There was a problem hiding this comment.
| 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. | |
| The moment something breaks, you'll know. Whether it's via Slack, email, PagerDuty, you'll get notified fast. |
I've been enjoying the cheekiness of the doc overall, but this one didn't land for me. Seems like an unnecessary add. Although if you do want something cute here, maybe "by fax" instead of smoke signal?
| 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. |
There was a problem hiding this comment.
Could this be a good opportunity to name-drop Seer (or at least the functionality)? Something like "and spin up a fix without leaving your flow. Or better yet, have AI do it."
| 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. |
There was a problem hiding this comment.
Also seems like it could be a good Seer feature drop moment!
|
|
||
| ## 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. |
There was a problem hiding this comment.
"We're admittedly partial to [Sentry's Error Monitoring]" - does this make sense in a Sentry doc? I do see how, after reading the doc again, we're staying neutral in describing what error monitoring is, but we're already here, in Sentry.
It would read more clearly if the section started with something more like "Here's how Sentry makes error monitoring a superpower in your developer toolbox".
There was a problem hiding this comment.
If we expect this to be an entry point doc for Sentry newbies, let's change the Prevent and Seer terms to something people understand. Prevent = AI-driven PR review bots. Seer = an issue autofix agentic AI.
There was a problem hiding this comment.
I'm digging the playful tone! I feel conflicted with how Sentry-neutral the doc is until the last paragraph. It's different from the rest of the docs in the concepts section. Not a bad thing, but I wonder if we can sprinkle in a little more foreshadowing to the end paragraph. And we should be punching up how modern error monitoring includes leveraging AI tools to make debugging that much easier.
|
@sfanahata good call on the AI inclusion! I deliberately tried to make this brand agnostic until the final paragraph; I'm hoping people will come here to get their questions answered without it feeling too much like we are trying to sell them something, a very top-of-funnel strategy to introduce our brand as smart, fun, and helpful. |
Co-authored-by: Shannon Anahata <[email protected]>
Co-authored-by: Shannon Anahata <[email protected]>
|
Makes sense. It just feels somehow off being in our documentation? But also doesn't hurt anything to have it there! |
DESCRIBE YOUR PR
See new page: https://sentry-docs-git-concepts-em.sentry.dev/concepts/key-terms/error-monitoring/
Please let me know how you feel about the tone here, I tried to make it fun and light but still communicate the concepts clearly.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES