- How do I install changole/otel-logging in a Laravel app?
- Install it with Composer, publish the package config if provided, then add the OTLP channel to config/logging.php and include it in your LOG_STACK or set LOG_CHANNEL. The assessment describes this as a small happy path: composer require, publish config, add a channel entry, and flip LOG_CHANNEL or LOG_STACK. Confirm the exact publish tag and config keys in the README before changing production logging.
- Does changole/otel-logging add trace_id and span_id to Laravel logs?
- The package is intended to provide trace correlation, which is the key architectural value described in the assessment. However, the evaluation explicitly asks the maintainer or code review to confirm whether the handler injects the active span context or only static resource attributes. Do not assume correlation works until you verify that trace_id and span_id are read from the active OpenTelemetry span and attached to each log record.
- What Laravel and PHP versions does this OTLP logging package support?
- The assessed stack target is Laravel 10, 11, or 12 on PHP 8.2+ with Monolog 3 and PSR-3. The assessment flags Monolog major-version drift as a medium risk, so confirm Monolog 3.x support rather than assuming Monolog 2-only handlers will work. Check the package composer.json and README for the authoritative compatibility matrix.
- Is changole/otel-logging safe to use in commercial Laravel projects?
- There is a blocker in the assessment: the repository has NOASSERTION for license, meaning no declared license gives no clear legal right to use, modify, or redistribute it in a commercial codebase. Resolve the license question with the maintainer or legal team before evaluation continues. Even after licensing, consider the single-maintainer bus factor and lack of community validation.
- Does the package export logs synchronously on every request?
- The assessment warns that blocking export on the request path is a medium risk: synchronous OTLP HTTP export adds a collector round-trip to every request unless it is batched or deferred to shutdown. Ask whether the handler exports per record, batches, or flushes at terminating. Test collector latency and failure behavior before enabling it for all traffic.
- What happens if the OpenTelemetry collector is down or times out?
- The evaluation lists this as an open review question: does a failed export throw and break the request, or fail silently and degrade to the fallback channel? You should verify the handler's exception behavior and configure a fallback channel for resilience. Do not route critical production logs through the OTLP channel until timeout and failure semantics are confirmed.
- Does changole/otel-logging work with Laravel Octane, Horizon, and queue workers?
- There is no community validation yet, so the assessment explicitly flags unknown behavior in Octane, Horizon, and high-volume queue workers. The key concern is whether the batch buffer ever flushes in a long-running Horizon worker. Test long-running processes and ensure exports flush on termination or at safe intervals.
- Should I use changole/otel-logging or the official OpenTelemetry Monolog handler?
- If this package is a thin wrapper over open-telemetry/opentelemetry-logger-monolog, the assessment recommends adopting the upstream handler directly and avoiding the bus-factor-1 dependency. Compare it with keepsuit/laravel-opentelemetry for broader Laravel auto-instrumentation, or a collector filelog receiver on existing daily logs if you do not need trace correlation. Choose based on whether you need the Laravel channel integration or just OTLP log shipping.
- Which OpenTelemetry PHP SDK version and OTLP transport does it use?
- The assessment says to verify which open-telemetry/* packages and versions are pinned and whether the PHP logs SDK is still experimental. It also recommends confirming whether the transport is OTLP/HTTP with protobuf or gRPC; HTTP/protobuf is more portable because it does not require ext-grpc. These details affect deployment blockers and long-term upgrade risk.
- How do I test changole/otel-logging before production?
- Start with a staging collector and a small non-critical channel in your Laravel logging stack, then verify resource attributes such as service.name and deployment.environment. Check that structured context and trace IDs appear in the backend, and test collector timeouts, fallback behavior, and long-running workers. The assessment also asks whether there is CI, a test suite, and coverage for exception rendering and context array serialisation, so review the repository tests before relying on it.