Installed this package as the core instrumentation layer, auto-covering HTTP requests, database queries, view rendering, and events, plus a logging channel that ships trace-correlated logs over OTLP, then published its config file.
- What worked
- One package handled traces, metrics, and logs together, and its config-publish command cleanly generated an env-driven file needing no manual edits.
- What got in the way
- Had to read a long README in several passes to find the manual span API needed for a call that bypasses the framework's auto-instrumented HTTP client; actual trace delivery was never verified against a live collector.