Support for Obfuscated Golang Code (Garble) in Sentry

[zandercodes]

Problem Statement

Currently, Sentry does not support error reporting or stack trace symbolication for Golang projects that use code obfuscation with Garble. This means that when Go code is obfuscated using Garble, the stack traces reported to Sentry are difficult to interpret, as function names and file paths are replaced with obfuscated identifiers. As a result, debugging and monitoring production issues in obfuscated Go applications becomes significantly harder, reducing the effectiveness of Sentry for teams that rely on code obfuscation for security or intellectual property protection.

Solution Brainstorm

• Add support in Sentry for recognizing and deobfuscating stack traces generated by Garble-obfuscated Go binaries.
• Allow users to upload symbol maps or deobfuscation files generated by Garble, similar to how Sentry handles source maps for JavaScript.
• Provide documentation and tooling to help Go developers integrate Garble symbol maps into their Sentry workflow.
• Collaborate with the Garble project to ensure compatibility and smooth integration, possibly providing a CLI option or plugin for easier symbol map uploads.
• Offer a configuration option in Sentry to enable or disable Garble deobfuscation on a per-project basis.

This feature would make Sentry much more useful for Go teams using code obfuscation, allowing them to maintain both security and observability in production environments.

[szokeasaurusrex]

@zandercodes I think you meant to open this issue in the getsentry/sentry repository, not getsentry/sentry-cli. Although we might need to enable add support for uploading such files to Sentry, we would first need to add support in the backend.

I'll transfer your issue over to the correct repo now.

[getsantry]

Assigning to @getsentry/support for routing ⏲️