OpenTelemetry Observability Stack

GENERALArchitecture
OpenTelemetry Observability Stack — GENERAL architecture diagram

About This Architecture

Three instrumented microservices propagate a single trace ID across their call chain while emitting traces, metrics, and logs from their OpenTelemetry SDKs into a shared OpenTelemetry Collector, which fans the three signal types out to dedicated tracing, metrics, and log backends — showing how OTel unifies instrumentation across the whole observability stack instead of requiring separate agents per signal.

Architecture prompt

Three instrumented microservices propagate a single trace ID across their call chain while emitting traces, metrics, and logs from their OpenTelemetry SDKs into a shared OpenTelemetry Collector, which fans the three signal types out to dedicated tracing, metrics, and log backends — showing how OTel unifies instrumentation across the whole observability stack instead of requiring separate agents per signal.

Generated by Diagrams.so — AI architecture diagram generator with native Draw.io output. Fork this diagram, remix it, or download as .drawio, PNG, or SVG.

Generate your own architecturediagram →

About This Architecture

Three instrumented microservices propagate a single trace ID across their call chain while emitting traces, metrics, and logs from their OpenTelemetry SDKs into a shared OpenTelemetry Collector, which fans the three signal types out to dedicated tracing, metrics, and log backends — showing how OTel unifies instrumentation across the whole observability stack instead of requiring separate agents per signal.

OpenTelemetry Observability Stack

AutoCurated TemplateMonitoring
0 views0 favoritesPublic

Created by

July 2, 2026

Updated

July 2, 2026 at 5:24 PM

Type

architecture

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI