From HAR to OpenTelemetry Trace: Redefining Browser Observability
summary
Describes a pipeline that converts HTTP Archive JSON into OpenTelemetry traces, batches and enriches spans, and routes them via an OpenTelemetry collector chain to backends like Jaeger. Implementation reads HARs from Kafka, maps each request to a client span with semantic-convention attributes, omits headers for privacy, attaches ThousandEyes resource IDs and permalinks, and filters/duplicates per integration. Demo shows page loads for fisco.com visualized in Jaeger. Key components: HAR→OTLP converter, dual-collector architecture.
AI-written summary · about
chapters (8)
- 0:00OpenTelemetry and HAR files
- 3:29What is HAR and limits
- 4:52ThousandEyes HAR data
- 6:59HAR to OpenTelemetry traces
- 9:28ThousandEyes trace architecture
- 13:22Demo: Export traces to Jaeger
- 15:27Trace data use cases
- 16:53Key lessons and insights
related talks
12m⚡ Lightning Talk: From HAR To OpenTelemetry Trace: Redefining Your Observability
40mPractical introduction to OpenTelemetry tracing
38mPractical introduction to OpenTelemetry tracing
35mOpenTelemetry for Busy People
55mCloud-Native Observability with OpenTelemetry
37mBeyond Getting Started: Using OpenTelemetry to Its Full Potential
43mPractical Introduction to OpenTelemetry Tracing
41mPractical introduction to OpenTelemetry tracing