SQS instrumentation is supported out of the box with the Helios OpenTelemetry SDK.
Below are a few examples of how you can leverage this E2E observability in Helios.
When searching for the
SQS component you will see all services and traces that include handling SQS messages. The traces are grouped by APIs (if a message is consumed by the service) and Outgoing operations (if a message is produced by the service).
When using trace visualization, it's very easy to see the E2E flow of operations (spans) handled by different SQS message queues.
In addition to tracing E2E applicative flows, Helios provides you with the insight and tools to investigate slow processing times of messages across your distributed application.
Currently supported in the Helios OpenTelemetry SDK for Node.js version 1.0.89 or newer.
Queue latency is calculated at the instrumentation level and thus can be handled as all other span properties are, through the labels, alerts and notifications mechanism in Helios.
Queue latency is also easily available on the trace visualization, for any span consuming a message from a queue (and specifically, Kafka).
Also, each API that is essentially the service consuming a message - now includes the queue latency distribution widget as part of the API dashboard. Clicking on each bar takes you to the relevant traces with the corresponding queue latency time.
Coming soon for SQS. Learn more on Kafka.
Helios is a a dev-first observability platform that helps dev and ops teams shorten the time to find and fix issues in distributed applications. Built on OpenTelemetry, Helios provides traces and correlates them with logs and metrics, enabling end-to-end app visibility and faster troubleshooting.
Get started for free with Helios to simplify and enrich OpenTelemetry distributed tracing.
Updated 6 months ago