Skip to main content

Alerta alerts

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

  • url โ€” Alerta server URL.
  • apiKey โ€” API key.

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
urlstringyesnourlโ€”Alerta server URL
apiKeystringyesyesโ€”โ€”API key
environmentstringnonoโ€”ProductionEnvironment (default: Production)
servicestringnonoโ€”kwatchService name (default: kwatch)
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:
alerta:
url: <url>
apiKey: "${file:/config/alerta-apiKey}"

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.