
Sentry SDK for Godot
https://github.com/getsentry/sentry-godot- Category
- Developer Tools
- Rank
- No. 394Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- getsentry
- GitHub
- 252 stars
- Latest release
- 2.1.1
- Date
About
Capture crashes and errors from your Godot game with the official Sentry SDK — get stack traces, breadcrumbs, and performance data.
What it does
A native Godot extension that monitors game health during testing and production. It automatically reports failures and associates them with release, hardware, user, attachment, and feedback context. Platform-specific Sentry components carry the telemetry to real-time alerts and a web dashboard.
Why it's ranked here
A strong choice for teams already using Sentry and shipping Godot across several targets. The official extension spans desktop, mobile, web, GDScript, and C#, while exposing configuration inside Godot. Its platform-specific build layers add complexity, but the repository documents and tests them seriously.
What's good
Coverage goes beyond basic failures: release tracking, hardware details, user feedback, attachments, metrics, logging, and hang detection are represented. Prebuilt extension libraries reduce setup work. The project also maintains editor-integrated class documentation and separate tests for GDScript, native code, managed code, Android, web, and end-to-end behavior.
Tradeoffs
Current major releases require Godot 4.5 or later. Building from source needs several toolchains, with extra Android, Apple, web, and managed-language steps. Platform behavior is not perfectly uniform: the newly documented scoped telemetry is discarded with a warning on macOS and iOS.
How to use it well
Use it when a Godot team needs operational evidence from QA builds and released games, especially across multiple platforms or both GDScript and C#. Start with the prebuilt addon, configure it through project settings, and test reporting before release. It complements automated testing and player support workflows; it does not replace either.
Technical notes+
src/register_types.cpp registers public Godot classes plus backend-specific native, Android, Cocoa, and JavaScript implementations, creates the SentrySDK and SentryUnit singletons at scene initialization, and auto-initializes the SDK. SConstruct selects the backend by platform, builds shared GDExtension libraries, separates debug symbols, emits the extension manifest, and offers Android, iOS, and JavaScript bundle targets. CONTRIBUTING.md documents GDScript tests under project/test/, C++ tests under tests/cpp/, .NET tests under tests/dotnet/, integration tests under tests/integration/, and Playwright infrastructure under tests/web/. Sentry.Godot.slnx includes the managed library, analyzers, source generator, demo project, and generator and analyzer tests.
Observed
- License
- MIT License
- Primary implementation
- C++ GDExtension library with platform-specific backends
- Install surface
- Prebuilt extension libraries and a demo project are distributed through GitHub Releases
- Interface
- Godot library with GDScript and C#/.NET APIs plus editor project settings
- Platform support
- Windows, Linux, macOS, Android, iOS, and Web
- Godot compatibility
- 1.x and 2.x releases require Godot 4.5 or later
- Test structure
- Separate GDScript, C++, .NET, integration, Android, and web test infrastructure
Read from README.md, Gemfile, src/register_types.cpp, site_scons/utils.py, gradlew, .craft.yml, LICENSE.md, SConstruct, gradlew.bat, CHANGELOG.md, .clang-format, .ruby-version, CONTRIBUTING.md, build.gradle.kts, Sentry.Godot.slnx.
What it can do
Capture game crashes
Godot game runtime crashes → Crash reports with stack traces
Monitor application errors
Runtime errors and exceptions in Godot games → Error reports with contextual information
Track user interactions
Game events and user actions → Breadcrumb trail showing sequence of events leading to issues
Collect performance metrics
Game performance data during runtime → Performance monitoring reports and analytics
Generate stack traces
Code execution flow when errors occur → Detailed stack trace information for debugging
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.