Sentry is a real-time crash reporting and performance monitoring platform that helps developers track, triage, and fix errors in web, mobile, and backend applications. Supporting virtually all major programming languages and frameworks (JavaScript, Python, Java, Go, iOS, Android, Unity, etc.), Sentry captures detailed stack traces, breadcrumbs, user context, release information, and device metadata for each crash or exception. Teams can define alert thresholds, create issue grouping strategies, and integrate crash data with partner tools such as Slack, Jira, GitHub, and PagerDuty. Performance monitoring features include transaction tracing, span breakdowns, slow query detection, and alerting. With customizable dashboards and rich contextual data, Sentry transforms error insights into actionable development tasks and accelerates Mean Time To Resolution (MTTR). A fully managed SaaS offering also exists, as well as a self‑hosted version for teams with data sovereignty requirements.

Sentry is only partially available in mainland China. The SaaS endpoints hosted on Sentry.io (US and EU) are often blocked or throttled, causing SDK data submissions to timeout or fail. This results in gaps in error visibility and delayed alerts. Many Chinese teams work around this by deploying Sentry’s open‑source on‑premise version behind a self‑hosted Relay within China to proxy events to Sentry’s cloud, though this adds significant operational overhead. Alternatively, domestic crash‑monitoring services such as Bugly, Baidu MTC, or Aurora Crash Analytics are widely used—they offer faster data submission, full Chinese language support, and localization for local ecosystems. Cross‑region apps may implement dual reporting logic: using Sentry abroad, and a China‑native service domestically, to balance feature completeness and compliance.

The information regarding service availability in China is provided for general reference purposes only. Due to the dynamic nature of network conditions and regulatory environments, the actual accessibility of these services may vary over time and by location. Users are advised to verify the current status independently.