Desarrolladores de software Investigate production errors, crashes, stacktraces, logs, performance, and session replays through the Sentry CLI (the new `sentry` binary — NOT legacy `sentry-cli`). Reach for this whenever you need ground truth about what is failing in production: triaging or debugging a real error/crash/exception, pulling a stacktrace or root cause for a reported bug, checking what broke after a deploy, inspecting production logs, finding slow endpoints/transactions, watching a live error stream, confirming a fix actually stopped an error, or whenever the user mentions Sentry, an issue short-id (e.g. PROJ-1234, API-7), a sentry.io URL, "check prod errors", "what's erroring", "why is X crashing/timing out in prod", "is the deploy healthy". Strongly prefer this over guessing about runtime failures you cannot reproduce locally — Sentry holds the real stacktrace, tags, breadcrumbs, frequency, and AI root-cause analysis.
2026-06-23