Using Claude Code or similar agentic dev-tool?
The easiest way to integate is to use the Integrate with AI prompt.
You can collect errors by integrating your Sentry SDK with Better Stack. This allows you to leverage your existing Sentry setup to send errors to our platform for centralized management and analysis.
The easiest way to integate is to use the Integrate with AI prompt.
To configure Sentry SDK integration:
To send errors to Better Stack, configure your Sentry SDK according to the Data ingestion tab for your application:
Here are a few examples for popular Sentry SDKs:
Event ingestion works out of the box for Flutter and Dart. How readable your stack traces are depends on how you build:
--obfuscate --split-debug-info) and native iOS and Android crashes need debug symbols (iOS dSYMs, Android ProGuard/R8 mappings, and Dart symbol files) to be symbolicated. Better Stack does not support debug symbol upload yet, so frames in these builds won't be symbolicated.By default, errors from the Sentry SDK are not correlated with OpenTelemetry (OTel) traces because they use different IDs.
To link them in Better Stack, inject the OTel trace_id and span_id into the Sentry event context using the before_send callback. This provides a unified view of your telemetry data.
Here’s how to implement this for various languages:
The Sentry SDK versions listed below are the minimum supported. If you're using an older version, please upgrade before sending data to Better Stack.
| Platform | Minimum Version |
|---|---|
| JavaScript | 7.0.0 |
| Python | 2.0.0 |
| Ruby | 4.0.0 |
| Java/Android | 3.0.0 |
| Cocoa (iOS/macOS) | 6.0.0 |
| .NET | 3.0.0 |
| PHP | 4.0.0 |
| Go | 0.1.0 |
| React Native | 3.0.0 |
| Dart/Flutter | 8.0.0 |
After running the script, you should see your first report in Errors 🚀
We use cookies to authenticate users, improve the product user experience, and for personalized ads. Learn more.