Guides services where a single logging call fans out to multiple side effects - error tracking (e.g. Sentry), a centralized log-shipping endpoint, and chat/webhook alerting - rather than just writing a log line. Use when adding a log statement to a service with this shape, reviewing why removing a "log statement" broke alerting, or designing observability for a service with more than one logging sink.
