CakePHP Log Engine and HTTP Exception Boundary: Deduplication Policy

Short answer

CakePHP's log engine should not be the component that decides whether an exception pages someone. The ErrorHandler middleware and application logging operate at different boundaries, and the framework's default behavior is append-only: the ErrorHandler logs uncaught exceptions at error, while application code may log the same exception earlier in a try/catch. Deduplication is a policy decision, not a native feature of the core log engines. The safest split is: the ErrorHandler renders the exception into a response and logs it once; application code should not log the same exception again at the same level. If you need paging, route only error/critical to a notification engine, and make that engine stateful enough to suppress repeats. For CakePHP 4/5, the practical approach is to let the ErrorHandler keep ownership of the exception, and to use a custom log engine to summarize repeats into a single high-signal entry.

What criteria should decide when an exception becomes a page?

Use a product-level policy that is independent of the logging boundary. The transition from diagnostic to alert should be based on impact, not on whether the exception was caught by middleware or by application code. A reasonable rule is: page on error and critical, and exclude info and debug from paging. The key is to enforce this at the routing layer, not by asking each component to dedupe on its own.

How to avoid duplicate notifications

Duplicate alerts happen when the ErrorHandler and application code both log the same exception at the same level. The cleanest fix is to pick one owner. In practice, that means: let the ErrorHandler log the exception once, and ensure application code does not also emit the same exception at error. If you need application-level context, log it at info or debug and keep error for the ErrorHandler. That preserves the boundary and prevents the same event from being emitted twice.

How to summarize repeated exceptions into one high-signal entry

Core CakePHP log engines are append-only writers. To summarize repeats, implement a custom engine extending BaseLog that keys entries by a hash of the exception class, message, and request context, then emits a single entry with a count and a sample of the repeated exceptions. The engine can use Redis or APCu to track repeats, but this adds state and latency, so it should be scoped to the alert path only. Verify by triggering a controlled exception and checking that the ErrorHandler and application code do not both emit at the same level. If you disable the ErrorHandler's automatic logging, you risk silent failures, so only do that if your application-level logging is guaranteed to catch and log the exception. For CakePHP 4/5, confirm the exact Log configuration keys in config/app.php, since the framework's defaults and type-hinting can differ slightly between versions. The recommendation changes if you need to preserve request context for downstream diagnostics; otherwise, keep the ErrorHandler as the single owner of the exception and use a custom engine to summarize repeats.