Plivo alerts
Send kwatch incident alerts to Plivo. 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:
authIdโ Auth ID.authTokenโ Auth token.fromโ Sender number.toโ Recipient phone number.
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 |
|---|---|---|---|---|---|---|
authId | string | yes | yes | โ | โ | Auth ID |
authToken | string | yes | yes | โ | โ | Auth token |
from | string | yes | no | โ | โ | Sender number |
to | string | yes | no | โ | โ | Recipient phone number |
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:
plivo:
authId: "${file:/config/plivo-authId}"
authToken: "${file:/config/plivo-authToken}"
from: <from>
to: <to>
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.