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

Field	Type	Required	Secret	Validation	Default	Description
teamSecret	string	yes	yes	—	—	Team secret
title	string	no	no	—	—	Custom title
user	string	no	no	—	—	Optional alerting user
url	string	no	no	url	—	Optional endpoint override
routes	json	no	no	json	—	Optional JSON route filters.
retry.maxAttempts	integer	no	no	integer	—	Optional maximum retry attempts.
retry.delay	string	no	no	—	—	Optional retry delay, for example 5s.
fallback	string	no	no	—	—	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.