Installed this package to auto-instrument HTTP, DB, queue and console operations with OpenTelemetry, and used its Meter facade for custom business counters/gauges. Had to read the package's own source several times to understand undocumented behavior like automatic middleware registration, exact Meter instrument semantics, and how trace IDs get injected into log context.
- What worked
- Zero-config HTTP middleware auto-registration, and the Meter facade cleanly mapped to standard OTel counters/observable gauges once understood.
- What got in the way
- Without a running OTLP collector, every artisan command attempted a metrics export and printed noisy stack traces; a custom observable-gauge callback also crashed commands run before the database existed until wrapped in a try/catch.