ClickStack Demo Day (2026-08-28) - Notification channels for alerts

An alert can notify up to ten webhooks, but the alerts page rows and the alert detail header both read the legacy single-value mirror of the first channel. A multi-target alert rendered as though it notified one, labelled with a generic "Webhook" rather than the webhook's name. Dispatch was always correct, so this was a reporting gap. It pointed the wrong way, though: someone checking which targets an alert notifies was shown one, and would reasonably conclude a channel hadn't saved. Both surfaces now resolve every configured channel and name each target, so you can see at a glance which channels an alert notifies from the alerts list. Adding and removing channels, webhooks and incident.io integrations among them, is easier from the alert itself, and notification time is now attributed per target so you can tell which one was slow. Underneath, configured channels are notified directly rather than round-tripped through webhook mention strings appended to the message body. That round-trip was lossy, and it carried a live bug: configured channels were appended after whatever you wrote, so a body containing enough ad hoc mentions consumed the per-event notification cap and starved the alert's own channel. The alerts pages had accumulated enough buttons to be overwhelming, so the row actions, export and Terraform included, are consolidated behind a single menu. Part of the ClickStack Demo Day series. See the full post at https://clickhouse.com/docs/use-cases/observability/clickstack/demo-days/2026/2026-08-28