New Alerting Webhook Options: Follow Redirects & Allow Insecure

Alerting Webhooks now support automatic redirect following and connections to internal/dev endpoints with self-signed certificates (use the latter with extreme caution).

We've added two new settings to alerting webhooks for greater flexibility:

Follow Redirects: Enable this to automatically handle HTTP 3xx redirect responses from your endpoint, ensuring smoother alert delivery for services using redirects (e.g., for load balancing or HTTPS enforcement).
Allow Insecure (Non-Production Only): This option permits connections to development or internal services using self-signed/private SSL/TLS certificates by bypassing certificate validation. Crucial Security Warning: Enabling "Allow Insecure" exposes your connection to Man-in-the-Middle (MITM) attacks.
- NEVER transmit sensitive data with this option active.
- Strictly for non-production environments. Do NOT use in production.

Find these new options in your alerting webhook configurations:

An example of a webhook that has been configured to follow redirects and allow insecure requests.

Back to Changelog