E_DEPRECATED noise in production error_log

Managing the balance between system stability and log volume in PHP 8.x requires precise configuration of the error_reporting directive. While E_ERROR and E_WARNING are essential for identifying immediate failures, E_DEPRECATED notices often flood logs during major version transitions without impacting current runtime execution.

The goal is to maintain a clean production log while ensuring that future-breaking changes are not entirely ignored. Relying solely on log_errors without specific level filtering can lead to excessive disk I/O and obscured critical failures.

Configuration Uncertainty

There is a conflict between the need for long-term maintenance visibility and the requirement to minimize notification noise in high-traffic environments.

• What is the recommended error_reporting bitmask to isolate fatal errors while selectively capturing deprecation warnings?
• Can a custom set_error_handler effectively throttle repeated E_DEPRECATED messages without missing unique occurrences?