> Markdown version of [/videos/841-hands-on-with-opentelemetry](https://www.wearedevelopers.com/videos/841-hands-on-with-opentelemetry). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Hands on with OpenTelemetry

Is microservice complexity turning your architecture into chaos? Discover how OpenTelemetry standardizes metrics, logs, and traces to prevent vendor lock-in and radically simplify distributed debugging.

- **Speakers:** Nočnica Mellifera
- **Event:** WeAreDevelopers LIVE
- **Published:** December 15, 2023
- **Duration:** 53:57
- **URL:** https://www.wearedevelopers.com/videos/841-hands-on-with-opentelemetry

## Summary

The transition from monolithic applications to microservices has significantly increased architectural complexity, frequently turning staging environments into production-like testing grounds. Observability—fundamentally defined as the "time to understanding" an anomaly—is a critical capability for reducing system chaos. The OpenTelemetry project addresses this complexity by standardizing how application telemetry, encompassing metrics, logs, and traces, is generated and transmitted across distributed networking stacks. Instead of locking teams into proprietary data storage or visualization tooling, this architecture standardizes data collection at the instrumentation layer, allowing application performance management tools to function interchangeably.<br><br>At the core of this standard sits the OpenTelemetry collector, a vital component that decouples data generation from backend storage. Microservices transmit raw signals via the OTLP standard to this collector, which operates as a robust pipeline of receivers, processors, and exporters. Processing telemetry at this intermediate stage enables teams to control metric explosion by sanitizing high-cardinality metrics, such as specific user IDs embedded in page paths. Furthermore, filtering PII or massive trace attributes purely via collector configurations ensures that application codebases remain free of ad-hoc filtering logic.<br><br>While the vast majority of raw distributed traces are rarely viewed by humans, the underlying context propagation serves as a highly scalable connective tissue across separate APIs. Using OpenTelemetry "baggage," developers can seamlessly pass custom metadata throughout an entire request trace to dictate smart routing or specific testing scenarios. Even as raw logging remains the default diagnostic tactic for many developers, explicitly tying logs to uniform trace IDs radically simplifies distributed debugging tasks. Ultimately, OpenTelemetry strictly handles internal application telemetry, meaning platforms require external synthetic monitoring capabilities to act as a decisive behavioral backstop when internal performance metrics fail.

**Keywords:** opentelemetry architecture, observability engineering, high cardinality metrics, microservice monitoring, opentelemetry collector, otlp transmission, distributed tracing, context propagation, opentelemetry baggage, metric explosion, telemetry pipeline, synthetic monitoring, log routing, application performance management

## Chapters

1. **Understanding observability and time to understanding metrics** (00:18) — How observability calculates the speed of discovering an issue and understanding its underlying mechanism.
1. **Understanding why microservices complicate system observability architecture** (04:30) — How the shift from monolithic patterns to chaotic microservices creates extreme system mapping complexity.
1. **Centralizing data with the OpenTelemetry collector component** (07:25) — How the OpenTelemetry collector standardizes and collates code-level instrumentation data across microservice environments.
1. **Capturing system overviews using broad statistical metrics** (11:19) — Why metrics serve as an easy-to-store baseline solution for tracking high-level system behaviors.
1. **Integrating existing application logs into OpenTelemetry pipelines** (12:14) — How standard log collection remains a primary observability method that feeds directly into automated collector pipelines.
1. **Connecting microservice requests via standardized distributed tracing** (15:17) — Connecting stateless microservice time spans to analyze full request propagation paths automatically.
1. **Managing metric explosion from high cardinality data variables** (18:49) — Balancing specific user variables against massive database storage spikes caused by namespace explosion.
1. **Filtering observability data dynamically without altering codebase logic** (24:03) — Configuring automatic tools to filter out sensitive attributes without maintaining individual code-level trace adjustments.
1. **Configuring receivers, processors, and exporters inside the collector** (28:00) — Combining multiple routing stages inside collector pipelines to scrub sensitive tracing fields.
1. **Connecting individual contextual spans into end-to-end trace waterfalls** (32:47) — Generating a complete trace history mapping by matching unique transaction headers against processed time events.
1. **Passing contextual system variables using OpenTelemetry baggage traces** (33:49) — Adding generalized execution context tags to tracing headers for smart routing or container security validation.
1. **Understanding out-of-scope execution capabilities for the OpenTelemetry standard** (35:45) — Distinguishing pure data transmission specifications from external dashboarding limits, alerting services, and uptime monitoring.
1. **Supplementing internal application tracing with comprehensive synthetic monitoring** (39:45) — Verifying realistic public infrastructure availability using programmable workflows independent of specific code instrumentation limits.
1. **Customizing external collector behavior utilizing static YAML programming** (41:51) — Using formatting configuration parameters to normalize conflicting data strings imported across diverse underlying frameworks.
1. **Managing redundant log verbosity levels and backend routing rules** (43:17) — Isolating debug errors to dedicated low-cost archives while preserving structured execution links internally.
1. **Evaluating practical OpenTelemetry downsides alongside pending transformation features** (46:45) — Identifying potential execution weaknesses in automatic language integrations compared to stable vendor options.
1. **Integrating OpenTelemetry pipeline platforms with embedded third-party observability providers** (49:11) — Verifying exact external ingestion support guarantees to ensure clean telemetry parsing across strict dashboard environments.
1. **Exploring advanced remote testing capabilities using robust Checkly scripts** (51:12) — Improving reliable external incident monitoring response workflows by customizing active execution test deployments directly.

## Related Moments

- [Defining OpenTelemetry as a standardized observability framework](https://www.wearedevelopers.com/videos/1232-observability-with-opentelemetry-elastic) (from "Observability with OpenTelemetry & Elastic")
- [Implementing tracing and metrics code with OpenTelemetry APIs](https://www.wearedevelopers.com/videos/386-telemetry-without-the-tool-tax) (from "Telemetry without the 'Tool Tax'")
- [Core architectural components of the OpenTelemetry data pipeline](https://www.wearedevelopers.com/videos/386-telemetry-without-the-tool-tax) (from "Telemetry without the 'Tool Tax'")
- [Gathering metrics natively with OpenTelemetry frameworks](https://www.wearedevelopers.com/videos/838-tips-techniques-and-common-pitfalls-debugging-kafka) (from "Tips, Techniques, and Common Pitfalls Debugging Kafka")
- [Distinguishing between telemetry, monitoring, and observability](https://www.wearedevelopers.com/videos/100158-the-opentelemetry-mistakes-i-keep-seeing-and-how-to-stop-making-them) (from "The OpenTelemetry mistakes I keep seeing (and how to stop making them)")
- [Tracing agent telemetry with OpenTelemetry and Jaeger tools](https://www.wearedevelopers.com/videos/1601-one-ai-api-to-power-them-all) (from "One AI API to Power Them All")

## Related Articles

- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)
- [Effortlessly Scale Prometheus With The Telemetry Data Platform – And Keep your Grafana Dashboards, Too!](https://www.wearedevelopers.com/magazine/3-effortlessly-scale-prometheus-with-the-telemetry-data-platform-and-keep-your-grafana-dashboards-too)
- [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it)
- [The CAMARA Project: How Telcos Collaborating Improves Developer Experience](https://www.wearedevelopers.com/magazine/671-the-camara-project-how-telcos-collaborating-improves-developer-experience)

## Related Jobs

- [Software Engineer, Platform Engineering (L2)](https://www.wearedevelopers.com/jobs/ext/1956829-software-engineer-platform-engineering-l2) at **Twilio**
- [Endpoint Security Engineer - OT](https://www.wearedevelopers.com/jobs/ext/1306782-endpoint-security-engineer-ot) at **ZEISS Group**
- [Lead Software Engineer - Data Engineering](https://www.wearedevelopers.com/jobs/ext/2000968-lead-software-engineer-data-engineering) at **Dynatrace**
- [Engineer, Offensive Security Organization](https://www.wearedevelopers.com/jobs/ext/1992296-engineer-offensive-security-organization) at **Twilio**
- [Software Engineer (L2) Segment Team](https://www.wearedevelopers.com/jobs/ext/238794-software-engineer-l2-segment-team) at **Twilio**
- [Software Engineer (L2) Segment Team](https://www.wearedevelopers.com/jobs/ext/209570-software-engineer-l2-segment-team) at **Twilio**