Skip to main content

Telegram alerts

Send kwatch incident alerts to Telegram. 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:

  • token โ€” Bot token.
  • chatId โ€” Chat ID.

For a guided setup, use the Telegram channel guide.

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
tokenstringyesyesโ€”โ€”Bot token
chatIdstringyesnosigned-integerโ€”Chat ID
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:
telegram:
token: "${file:/config/telegram-token}"
chatId: <chatId>

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.