OpenTelemetry End-to-End: Connect Traces to Hosts

Summary

Pixel shares a DEV Community article on extending OpenTelemetry observability from a user’s browser click through backend services to the host. It explains how Dynatrace SaaS accepts OTel telemetry and builds connected topology using context such as W3C trace propagation, helping teams investigate issues without manually stitching together signals.

DEV Community

OpenTelemetry end-to-end: from user click to host, without stitching the pieces together

Many teams have adopted OpenTelemetry for a good reason: no longer depending on a proprietary agent to instrument their services. The project has now graduated from the CNCF and has become the common framework for producing traces, metrics and logs. But once the SDKs are in place and the Collector is deployed, one question soon comes back: why is investigating still so laborious? That is the whole point of taking OpenTelemetry end-to-end, from the user’s click to the host. The answer fits in one sentence: OpenTelemetry standardises the shape of signals, not the relationships between them. A trace knows which service it comes from; it does not know which host that service runs on, which user session triggered it, or which AI model it calls downstream. Without that context, the on-call engineer makes the connections by hand, across several tabs. Dynatrace SaaS tackles the problem from the other end: it accepts OTel telemetry as is and automatically builds the topology that connects it. Let us look at what this brings in practice and which settings determine the result. Four seams to stitch back together In an architecture instrumented with OpenTelemetry, context breaks almost always happen in the same places. Between the browser and the first service Dynatrace frontend monitoring (web, mobile, cross-platform) connects to OTel-instrumented backends through standard W3C propagation, i.e. the traceparent and tracestate headers. No additional instrumentation is needed along the backend chain. You can then start from a session in User Events and Sessions (including its replay on Grail), open the associated trace in Distributed Tracing, or go the other way from a backend span to the user action that caused it. The condition, and it is often forgotten: the trace context must actually be propagated all the way to the service. Between services The cloud-native Service Map continuously discovers connections at runtime: upstream and downstream services, database queries, messaging flows, with health status overlaid. Service-to-database mapping is built from OTel data, with no manual entity modelling; it relies on dependencies actually observed rather than on tags. Between the application and the infrastructure For teams already running a Collector on their hosts, host and process metrics feed the Infrastructure & Operations app, with correlated logs and alert templates. Infrastructure entities join Smartscape, which makes it quick to tell an application problem from a platform problem. The documentation lists the supported Collector distributions; they must include the hostmetrics receiver and the resourcedetection processor. Between classic services and AI Community conventions for AI, such as OpenInference and OpenLLMetry, which belong to the OpenTelemetry ecosystem, allow Dynatrace to place models, agents and agent services in Smartscape, next to traditional services. Captured production telemetry can then serve as input to online evaluations of response quality, safety and performance, depending on the chosen configuration. OneAgent or OpenTelemetry: no need to choose Smartscape treats OneAgent and OpenTelemetry as equivalent sources: an OTel-instrumented service appears with the same depth as a service observed by OneAgent. That is a practical argument for hybrid environments, which are very common: one team keeps OneAgent on its legacy VMs, another instruments its microservices with OTel, and the topology stays unified. A note on scope: the Service Map, the frontend-backend link and host monitoring through the Collector are offered to customers on the Dynatrace Platform Subscription (DPS). In practice: OpenTelemetry end-to-end in Dynatrace Step 1 — Check propagation on the frontend side When the frontend calls an API on another domain, the browser only sends trace headers if the API explicitly allows them. Check your APIs’ CORS response: Access-Control-Allow-Headers: traceparent, tracestate, content-type
Also check that your gat...
OpenTelemetry End-to-End: Connect Traces to Hosts
Powered by Readybot.io

The latest from Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …