laravel:exception-handling-and-logging

To implement structured logging and exception handling in Laravel, define reportable and renderable exceptions that add domain-specific context to logs, route noisy errors to separate channels, and ensure API-friendly responses.

Routing noisy Laravel logs to separate channels involves configuring a channel-based logging strategy in your exception handler to isolate verbose errors, keeping the default log stream actionable.

Converting Laravel exceptions into API-appropriate responses is done within the renderable method of your exception handler by mapping domain-specific exceptions like ModelNotFoundException to structured API response formats.

Laravel exception handling works across web routes, API responses, and job queues by centralizing logic in reportable and renderable methods, ensuring uniform behavior for errors like DomainException and ModelNotFoundException.

To avoid logging secrets when adding structured context to Laravel exceptions, carefully map only domain-specific data within the reportable method, explicitly excluding sensitive request inputs from the log channels.