Skip to main content

SIGNL4 alerts

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

  • teamSecret โ€” Team secret.

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
teamSecretstringyesyesโ€”โ€”Team secret
titlestringnonoโ€”โ€”Custom title
userstringnonoโ€”โ€”Optional alerting user
urlstringnonourlโ€”Optional endpoint override
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:
signl4:
teamSecret: "${file:/config/signl4-teamSecret}"

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.