Skip to main content

Zulip alerts

Send kwatch incident alerts to Zulip. Use the interactive manager for installation and credential setup. This page explains the provider fields and shows a minimal configuration fragment.

Before you start, have these values ready:

  • email โ€” Bot email.
  • token โ€” Bot API key.
  • channel โ€” Channel/stream to post to.

Credentials, tokens, keys, passwords, and webhook URLs must be mounted from a Kubernetes Secret. Use an exact ${file:/absolute/path} reference for every field marked Secret.

Configurationโ€‹

FieldTypeRequiredSecretValidationDefaultDescription
emailstringyesnoโ€”โ€”Bot email
tokenstringyesyesโ€”โ€”Bot API key
channelstringyesnoโ€”โ€”Channel/stream to post to
urlstringnonourlhttps://zulip.example.com/api/v1/messagesServer URL (default: https://zulip.example.com/api/v1/messages)
titlestringnonoโ€”โ€”Custom title
routesjsonnonojsonโ€”Optional JSON route filters.
retry.maxAttemptsintegernonointegerโ€”Optional maximum retry attempts.
retry.delaystringnonoโ€”โ€”Optional retry delay, for example 5s.
fallbackstringnonoโ€”โ€”Optional fallback provider name.

Minimal exampleโ€‹

alert:
zulip:
email: <email>
token: "${file:/config/zulip-token}"
channel: <channel>

Add routes, retry, and fallback when you need delivery filtering or recovery. See the channels overview for guidance, or the complete provider reference for the catalog-wide view.