First OTel Instrumentation
Three signals.
Overview
OpenTelemetry instrumentation moves observability from vendor-specific SDKs to a standards-based one. Metrics, traces, and logs through a single SDK; same code works with Jaeger, Tempo, Datadog, New Relic, or any OTLP backend. The first instrumented service establishes conventions that every subsequent service inherits.
- Three signals through one SDK. Metrics, traces, logs. Full observability surface from a single integration.
- Vendor-neutral. Same SDK works with every major backend. Vendor swaps stop requiring re-instrumentation.
- Auto-instrumentation. Zero-code instrumentation for common frameworks (Java agent, Python
opentelemetry-instrument, etc). - Manual instrumentation plus OTel Collector. Custom spans and metrics for business-specific signals; collector handles the receive-process-export pipeline.
The approach
Three habits make OpenTelemetry produce real value rather than configuration churn: auto-instrumentation first for fast value, OTel Collector as the centralised pipeline, and vendor selected as the backend rather than the SDK.
- Auto-instrumentation first. Java agent, Python
opentelemetry-instrument, equivalent for other languages. Zero-code value before custom work. - OTel Collector as pipeline. Centralised receive-process-export flow. Backend flexibility lives here.
- Manual instrumentation for business spans. Custom spans and attributes for the work auto-instrumentation cannot see.
- Documented conventions plus vendor as backend. Span names, attributes, service names consistent; vendor chosen as a backend, not a lock-in.
Why this compounds
Each instrumented service inherits the conventions. The team’s observability fluency deepens; vendor changes stop requiring re-instrumentation; cross-service tracing surfaces incidents that single-service dashboards would miss.
- Vendor-neutral. Backend changes do not require re-instrumenting code.
- Cross-service visibility. Standardised telemetry crosses service boundaries. MTTR drops on incidents that span services.
- Reusable patterns. Standard instrumentation conventions transfer between services.
- Year-one investment, year-two habit. First service is heavy lift. By the third, the OTel template is settled.