- How do I install bilfeldt/laravel-http-client-logger in a Laravel app?
- Install it with Composer using composer require bilfeldt/laravel-http-client-logger. Laravel package auto-discovery should register the service provider, then publish the config and define a dedicated log channel and redaction rules. Check composer.json for the supported Laravel and PHP matrix before rolling it out.
- Which Laravel versions does bilfeldt/laravel-http-client-logger support?
- Version 2.6.0 adds Laravel 13.x compatibility, and the release notes indicate no breaking changes. Confirm the full supported matrix, including whether Laravel 10, 11, and 12 remain supported, plus PHP requirements from composer.json before rollout.
- Does it log outgoing HTTP requests made with Laravel's HTTP client?
- Yes. It adds configurable middleware for Laravel's HTTP client and captures URLs, status codes, timing, headers, and payloads. It fits code using Illuminate\Support\Facades\Http; direct Guzzle usage outside Laravel's HTTP client would need separate instrumentation.
- Are sensitive headers and request bodies redacted by default?
- The package provides sensitive-data redaction and flexible logging options, but the provided assessment does not list exact default rules. Treat redaction as a policy you must verify in the config and source before production. Misconfigured redaction is a primary PII leakage risk, so test headers and bodies explicitly.
- Will logging slow down my HTTP calls in production?
- Logging can add overhead, especially with synchronous logging or large payloads, and log volume scales with outbound HTTP traffic. Use a dedicated channel, retention limits, sampling where available, and avoid logging large bodies. Validate latency and failure behavior in staging before broad rollout.
- Does it support sampling, async logging, or correlation IDs?
- The release assessment flags sampling, async logging, and correlation IDs as questions to verify rather than confirmed features. Version 2.6.0 is described as a compatibility update adding Laravel 13.x support, with no new runtime features noted. Check the package config and source, and add sampling or correlation at your log pipeline level if the package does not provide it.
- What happens if the logger fails during an HTTP request?
- The assessment does not confirm that logger exceptions are isolated from outbound HTTP calls, so test this failure path in staging. It lists logger exceptions affecting request flow and missing logs during failures as risks to verify. The 2.6.0 release itself is considered low risk because it is compatibility-only.
- Can I use it instead of a full APM or distributed tracing tool?
- No. It is lightweight, Laravel-native observability for audit and debug logs of outbound HTTP calls. It is not a substitute for distributed tracing, metrics, or centralized observability, though it can complement those tools.
- How should I configure log volume and retention for high-traffic apps?
- Define a dedicated log channel with retention limits, avoid logging large bodies, and use sampling where possible. Estimate centralized log ingestion cost before broad rollout because volume scales with outbound HTTP traffic. Assign an internal owner for redaction rules, retention, and upgrade validation.
- Is bilfeldt/laravel-http-client-logger actively maintained and safe to adopt?
- It is a small, single-purpose package with low ongoing maintenance, and 2.6.0 is a compatibility update for Laravel 13.x with no breaking changes indicated. Community support means no vendor SLA and single-maintainer open-source risk should be acknowledged. Pin the version, monitor releases around Laravel compatibility, and assign an internal owner.