What is Sentry?
Turkish: Sentry
Sentry groups application errors with stack traces, releases, environments, and user impact so teams can monitor production issues.
What is Sentry?
Sentry is an error monitoring platform that captures application failures with context, not just as raw log lines. It shows which release introduced an error, which browser or device saw it, how many users were affected, and the stack trace behind the failure.
In a JavaScript application, the Sentry SDK can capture an unhandled exception, map minified code back to readable source lines through source maps, and group similar failures under one issue. Backend services can add request data, user identifiers, environment details, and custom tags to make the event more actionable.
How Does It Work?
- SDK setup: A language or framework-specific Sentry SDK is added to the application.
- Event capture: Exceptions, performance traces, and custom messages are sent to Sentry.
- Issue grouping: Errors with the same root cause are grouped together.
- Release tracking: Teams see when an error started and whether it disappeared after a fix.
- Alerting: Critical thresholds can notify Slack, email, or incident channels.
Business Use
Sentry turns a support report such as “checkout is broken” into a stack trace a developer can investigate. It is especially useful in SaaS dashboards, e-commerce checkout flows, and mobile applications where user impact matters.
Error tracking is part of a broader monitoring strategy, but it is not the same as logging. Sentry should be configured with privacy in mind: scrub sensitive fields, avoid unnecessary personal data, and tune alert thresholds to prevent alert fatigue.
Related Terms
Infrastructure monitoring collects metrics from servers, networks, databases, and cloud resources to catch failure signals early.
LoggingLogging is the practice of recording runtime events from applications and systems — critical for debugging and monitoring.
MonitoringMonitoring tracks application and infrastructure metrics, logs, and alerts to detect problems before users or SLAs are affected.