Skip to content
OpenSourceSoftware.ai
Sentry logo

Sentry

getsentry · Observability

GitHub stars

45,665
—Awaiting first sync

Awaiting first sync

No measured star history yet

What is Sentry?

Sentry connects an application's errors with the evidence needed to fix them. Issues, traces, logs and replays sit together, so a developer can move from an alert to the line of code and the user session behind it.

Sentry is a debugging platform that helps developers detect, trace and fix issues in their software. It groups errors into issues and adds traces, logs, session replay and profiling, with official SDKs for JavaScript, Python, Ruby, PHP, Go, Java, Swift, .NET, Rust and many more.

Core capabilities

  • Group errors into issues with the context needed to reproduce and fix them.
  • Follow traces, logs, session replays and profiles from the same issue.
  • Instrument almost any stack with official SDKs, from web and mobile to game engines.

Issues with the context to fix them

Errors are grouped into issues with stack traces and surrounding context. Traces and spans, logs, session replay and profiling add detail on performance and user behaviour, and dashboards, releases, monitors and alerts help teams track the health of each deployment.

  • Errors
  • Tracing
  • Session replay
  • Profiling

SDKs for almost every platform

Official SDKs cover JavaScript, Electron, React Native, Python, Ruby, PHP, Laravel, Go, Rust, Java and Kotlin, Objective-C and Swift, .NET, C and C++, Dart and Flutter, Elixir and game engines such as Unity, Unreal and Godot.

  • SDKs
  • Web
  • Mobile

Source-available and self-hostable

Sentry's source code is published under the Functional Source License, which converts each version to Apache 2.0 after two years. Besides the hosted service at sentry.io, Sentry publishes a self-hosted package, which needs a sizeable server to run.

  • FSL
  • Self-hosted
  • Source-available

Where it fits

Use cases

  1. 01

    Catch errors before customers report them

    Add the SDK for your language, get alerted when a new issue appears, and see the stack trace and context needed to fix it.

  2. 02

    Find the cause of a slow request

    Follow a trace through services and spans to the code that slowed a request down, alongside related logs and profiles.

  3. 03

    See what a user saw when it broke

    Open the session replay attached to an issue to watch the steps that led to the error in a web or mobile app.