- What is caixingyue/laravel-star-log used for?
- Laravel Star Log is a lightweight Laravel package for structured logging, with a focus on outbound HTTP request logging and diagnostics through Guzzle middleware. It integrates with Laravel's native logging system and adds contextual data to make debugging and monitoring clearer. It is best suited to Laravel apps that need auditability or failure triage for outbound HTTP traffic.
- How do I install laravel-star-log with Composer?
- Install it with Composer using the package name caixingyue/laravel-star-log, then publish its configuration if the package provides config publication. The integration approach described for v2.0.1 also involves middleware registration for outbound HTTP logging. Verify the exact service-provider and middleware steps against the package README for your Laravel version.
- Which Laravel and PHP versions does laravel-star-log support?
- The provided compatibility notes list Laravel 12 and Laravel 13, Guzzle 7 and Guzzle 8.0.1+, PSR-7 2.x and 3.x, and Mobile Detect 4.8. The package's PHP constraint is not specified in the context, so confirm it in composer.json before adopting. Also check whether Laravel 13 support is production-ready for your timeline.
- How do I configure log channels and formatting in laravel-star-log?
- Laravel Star Log is described as configurable for channels and formatting, and it uses Laravel's native logging system. You should publish or review the package config to set destinations, enablement, and output format. Because the provided context does not include exact config keys, confirm them in the README or config file.
- Does laravel-star-log redact authorization headers, cookies, query strings, or request bodies?
- The provided context does not confirm built-in redaction for authorization headers, cookies, query strings, or request and response bodies. Treat redaction as a required validation item before logging real traffic. Review the package code and configuration, and add filtering if sensitive values could be written to logs.
- How does laravel-star-log log timeouts, DNS failures, TLS failures, and connection resets?
- The context says failure logging and diagnostics are part of the package's purpose, but it does not specify how timeouts, DNS failures, TLS failures, or connection resets are represented. Guzzle 8 failure metadata may differ from Guzzle 7, so connection-failure logs need validation. Exercise each failure path in a non-production environment and confirm the log fields you need.
- Is laravel-star-log compatible with Guzzle 8 and PSR-7 3?
- Version 2.0.1 expands support to Guzzle 8.0.1+ and PSR-7 3.x while retaining Guzzle 7 and PSR-7 2.x coverage. Guzzle 8 coverage is tied to Laravel 13 in the provided notes, so mixed dependency resolution should be checked in your lockfile. Test both success and failure paths because the release touches exception hierarchy and transport-statistics handling.
- How do I disable laravel-star-log so the middleware does not run?
- The package is expected to support disabling logging, but the technical evaluation notes that a disabled-logging callback bypass should be verified. Confirm that turning logging off prevents the failure-log middleware from still executing. Test the disabled state on both Guzzle 7 and Guzzle 8 if you use both stacks.
- What is the performance overhead of laravel-star-log under concurrent outbound HTTP?
- The provided context does not include benchmark data for concurrent outbound HTTP, so overhead is not quantified. Because it operates as Guzzle middleware, log volume and request latency should be monitored in staging. Canary the package and watch for added latency before promoting to production.
- Does laravel-star-log have a CI matrix for lowest and highest dependencies?
- The context raises the CI matrix as a key question but does not confirm that one exists. Teams should maintain their own compatibility checks for Laravel, Guzzle, PSR-7, and Mobile Detect versions. Also compare the package with Laravel's native HTTP client events and existing Monolog or OpenTelemetry tooling before adopting it.