Features
Introduce PagerDuty support for workflows running on Argo Workflows
With this release, Metaflow users can get events on PagerDuty when their workflows succeed or fail on Argo Workflows.
Setting up the notifications is similar to the existing Slack notifications support
- Follow these instructions on PagerDuty to set up an Events API V2 integration for your PagerDuty service
- You should be able to view the required integration key from the Events API V2 dropdown
- To enable notifications on PagerDuty when your Metaflow flow running on Argo Workflows succeeds or fails, deploy it using the --notify-on-error or --notify-on-success flags:
python flow.py argo-workflows create --notify-on-error --notify-on-success --notify-pager-duty-integration-key <pager-duty-integration-key>
- You can also set the following environment variable instead of specifying --notify-slack-webhook-url on the CLI everytime
METAFLOW_ARGO_WORKFLOWS_CREATE_NOTIFY_PAGER_DUTY_INTEGRATION_KEY=<pager-duty-integration-key>
- Next time the flow fails or succeeds, you should receive a new event on PagerDuty under Incidents (Flow failed) or Changes (Flow succeeded)
What's Changed
- fix: validate required configuration for Batch by @saikonen in #1483
- feature: add PagerDuty support for Argo Workflows by @saikonen in #1478
- Bump version to 2.9.10 by @saikonen in #1484
Full Changelog: 2.9.9...2.9.10