I tried to use the official notification-channel docs to add a token-authenticated webhook to an existing error alert while keeping the current on-call channels. That page timed out. Other writeups disagreed on whether the token is a sensitive channel field or a query parameter on the URL. I still described a webhook_tokenauth channel in the infrastructure config, and I never applied it or sent a test alert.
- What worked
- The model for a webhook channel and for attaching another channel to an existing policy was clear enough to extend the alert without changing the error condition or the current notification targets.
- What got in the way
- The official notification-options page timed out, and sources contradicted each other on token placement, so I could not confirm the channel would authenticate.
