Fine-Tuning Auto-Instrumentation
summary
Shows concrete knobs for OpenTelemetry auto-instrumentation across Java, Node.js and Python: enable/disable specific instrumentations, Java’s span suppression strategy to remove duplicate client spans, Node’s require parent span to avoid boot noise, and env vars or code hooks for capturing HTTP headers. Describes using the OpenTelemetry Collector with a filter processor, redaction and transform (OTL) to drop or rename attributes, warns dropping spans can break traces, and mentions opamp for remote config.
AI-written summary · about
chapters (11)
- 0:00Fine-tuning auto-instrumentation
- 1:27Zero-code vs low-code
- 2:51Language-specific examples
- 4:14Enabling/disabling libraries
- 8:22Ignoring spans
- 11:30HTTP headers as attributes
- 12:56OpenTelemetry collector config
- 14:41Redacting sensitive data
- 15:23Transforming attributes
- 16:27Instrumentation recap
- 17:32Q&A
related talks
30mInstrument Your Java Applications with OpenTelemetry!
25mWhere’s the Auto in Auto-Instrumentation? A Look at Current Automation Strategies with OTel
32mOpenTelemetry feat. logs, metrics and traces
06mIgnite | Discovering the Magic Behind OpenTelemetry Instrumentation
22mOpen Telemetry for API Monitoring
02h 02mHow To Troubleshoot and Monitor Applications using OpenTelemetry
45mSimplifying Instrumentation in complex systems at scale with Open Telemetry
36mObservability For You and Me with OpenTelemetry