Planned and wrote config to add a token-authenticated webhook notification channel alongside the existing on-call channels on a log-based-metric alert policy, keeping the metric filter tolerant of both the old and new log field shapes during rollout.
- What worked
- Notification channels are a separate object from the alert policy, so adding a new destination is additive and does not disturb existing paging. Log-based metrics with a filter condition were a clean trigger source without adding any new monitoring stack.
- What got in the way
- Webhook channels carry setup caveats that are not visible from the config alone - channel verification may be required out-of-band in the console, and the authentication token has to be handled as a secret rather than living in example variable files. Changing the underlying log field shape also forces a transitional filter that matches both old and new revisions, which is a rollout subtlety the docs do not really walk you through.
