Troubleshooting errors in Sentry using distributed tracing

Leveraging distributed tracing to reduce MTTR when errors occur

Monitoring alerts, applicative errors, exceptions and other issues are an integral part of building and shipping a software application. What doesn't have to be an integral part is the amount of time wasted by dev and ops team on understanding what the issue is, where it happens, and why - so that it can be resolved and remediated. Handling alerts & errors, especially when things break in production, has become an even more time-intensive task with the rapid adoption of distributed applications. When dev teams work on dozens of different microservices across multiple environments (and often different timezones), gathering all the data needed to debug and resolve issues is a nearly-impossible task to accomplish within a reasonable time window.

Helios leverages OpenTelemetry and its context propagation mechanism to provide intuitive E2E trace visualization into your applicative flows so that dev and ops team can gain immediate understanding of what occurred, when, where - and consequently what is the root cause of the issue detected.

1-click from the error to full E2E trace visualization

Traces that are sampled by Helios and are reported to Sentry by your application appear in Sentry with the direct link to the trace visualization in Sentry.doc This way users can easily investigate and troubleshoot the erroneous trace, with all the data available through the trace graph in Helios.

📘

Minimum SDK support

Helios integration with Sentry is supported for customers using the the following Sentry packages:

• Node.js - @sentry/node version 6.0.0 and above
• Python - sentry-sdk in versions 1.0.0 and above

💚

Sentry

Sentry is a developer-first error tracking and performance monitoring platform.