Tomas's wroclove.rb 2025 lightning talk, framed as extra context after an earlier talk on structured logging. Argues that any non-trivial Ruby application with an APM vendor (New Relic, etc.) is effectively a current or future OpenTelemetry user whether conscious or not, because vendors are switching to OTel. Covers why logs alone aren't enough (no cross-service connection), the classical logs/metrics/traces trio, the unified 'wide event' concept with spans and events, the OpenTelemetry collector glueing spans with the same trace ID and parent-span IDs across services, adding attributes and events to the current span in Ruby, and using open-telemetry logging integration so logger.info events belong to a span. Flags that OpenTelemetry is still evolving and the Ruby implementation is immature (logging is experimental), but recommends learning it anyway. Recommends 'a pretty awesome book' on creating custom traces.