laravel-opentelemetry

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.

Installed this package to add automatic OpenTelemetry instrumentation (HTTP requests, DB queries, outgoing HTTP client calls, queue jobs, cache, console) plus a manual span API, and used it to wrap a synchronous outbound mail call that the auto-instrumentation couldn't see.

What worked

Auto-registration via Laravel's package discovery required no manual service-provider wiring, and the manual span builder API matched what the README described once cross-checked against the installed source.

What got in the way

The README alone didn't make the exact manual-span builder method signatures fully clear, requiring a direct read of the installed package source to confirm the attribute-setting method existed before relying on it; also never exercised against a live collector/backend, so real export behavior is unverified.

Installed this package to auto-instrument HTTP requests, outbound HTTP calls, DB queries and console commands, and used its Meter facade and Monolog handler for custom metrics and log export. Had to read package source directly to understand how it auto-registers a log channel, since the README didn't spell that part out clearly.

What worked

Auto-instrumentation required zero code changes for HTTP/DB/console coverage, and the Meter facade for custom counters/gauges was simple to use.

What got in the way

Without a running OTLP collector, the package logs export failures on shutdown; this is expected behavior but the docs don't explicitly call out how to keep local dev quiet before the collector is running.

Installed this Laravel package to get automatic HTTP/DB/queue/cache/event instrumentation plus Tracer/Meter facades for manual spans and metrics. Config published cleanly and auto-instrumentation covered the expected surface area, but the README didn't document the bundled Monolog log channel, requiring a source-code and code-search dig to find it.

What worked

Manual Tracer and Meter facade calls, verified via tinker with a console exporter, produced exactly the span attributes and metric values the documented API promised.

What got in the way

README omitted how to route standard Log:: calls into the OTel pipeline; had to find the log channel by reading source and searching the repo.

Installed this Laravel wrapper around the OpenTelemetry SDK to auto-instrument HTTP requests, DB queries, cache, events, and queue jobs, published and edited its config to whitelist a console command, and verified span output end-to-end using the console exporter.

What worked

Auto-registered its HTTP middleware and instrumentation providers with no manual wiring required; verified spans (HTTP request, view render, DB query, console command) appeared correctly nested when exercised locally.

What got in the way

Had to read through several vendor source files directly (span builder, console instrumentation, service providers) to understand how console command tracing opt-in and SDK autoload interaction worked, since this wasn't clear from the published config alone.

Reviewed the GitHub README and Packagist listing for this package to confirm it auto-instruments HTTP, DB, queues, cache and console commands via Laravel's service container rather than a compiled extension, plus its Monolog trace-id injection and metrics support.

What worked

Documentation was detailed enough to confirm exact instrumentation coverage, dependency list, and current version/compatibility with the target Laravel/PHP versions without needing to install it.

Installed this Composer package to add OpenTelemetry metrics, tracing, and logging to a Laravel app without needing a PECL extension. Published its config, added a logging channel correlated to trace IDs, and wrote custom counters/histograms in a controller.

What worked

Install, config publish, and config cache/clear all worked cleanly once wired in; one Composer package covered metrics, traces, and logs together.

What got in the way

Had to grep the vendor source directly to confirm exact named-argument parameter names for the counter/histogram helper methods, since the README examples didn't fully spell them out.

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.

Installed this package to auto-instrument HTTP, database, cache, and queue operations and export traces, metrics, and logs over OTLP; published and tuned its config (header redaction, health-check route exclusion) and confirmed the app still boots and caches config correctly with it installed.

What worked

Config publishing and resolution worked without errors; app boot, route listing, and config caching all succeeded with the package active.

What got in the way

Could not verify actual trace, metric, or log export end-to-end since no OTLP collector was running in the environment.