Allow users to configure a local script or binary as a notification trigger. When an incident opens or resolves, Piro executes the script and passes event data via environment variables or stdin (JSON).
Use case: teams that use an in-house alerting system, a custom webhook proxy, or any tool not natively supported.
Proposed interface:
- Field: path to executable (e.g.
/opt/notify/alert.sh)
- Field: execution timeout (seconds)
- Event data passed as env vars:
PIRO_EVENT, PIRO_SERVICE, PIRO_STATUS, PIRO_INCIDENT_ID, etc.
- Non-zero exit code treated as delivery failure (logged, retried per trigger retry policy)
Security considerations:
- Script must be executable by the Piro worker process
- Path must be an absolute path (no shell expansion)
- Worker-only: custom scripts run on the worker node, not on the API server
Allow users to configure a local script or binary as a notification trigger. When an incident opens or resolves, Piro executes the script and passes event data via environment variables or stdin (JSON).
Use case: teams that use an in-house alerting system, a custom webhook proxy, or any tool not natively supported.
Proposed interface:
/opt/notify/alert.sh)PIRO_EVENT,PIRO_SERVICE,PIRO_STATUS,PIRO_INCIDENT_ID, etc.Security considerations: