Hi, I'm having issues using the Pager Duty webhook...
# ask-community
h
Hi, I'm having issues using the Pager Duty webhook under "Notifications" - I've set the "Notify Type" to "failure", but in the Prefect log file it complains: WARNING | apprise - Failed to send Pager Duty notification: Bad Request - Unsupported Parameters., error=400 and also: unexpected value; permitted: 'info', 'success', 'warning', 'failure' (type=value_error.const; given=prefect_default; permitted=('info', 'success', 'warning', 'failure')) - any idea what I'm doing wrong?
j
Hey! Could you give any more info about how you're using the block? self hosted vs cloud? etc
h
Hi Jake - I'm runing the prefecthq/prefect:2.10.12-python3.11 image in Docker. Under "Notifications", I added a "Pager Duty Webhook" that will run for "Crashed, Failed, TimedOut" states. I copy the API Key and Integration Key from PagerDuty. So very straight forward config. I then simulate a "Failed" condition. As soon as a have a scheduled flow run, I get the above mentioned issue. So it is triggering the notification.
j
It looks like
notify_type
might be incorrectly marked as optional in the UI for that notification type
can you try and save it with
notify_type="info"
?
h
This is in the logs of Prefect: WARNING | apprise - Failed to send Pager Duty notification: Bad Request - Unsupported Parameters., error=400 (after setting Notify Type to "info")
j
do you mind keeping relies to the thread? It helps keeps the channel uncluttered 😄 Is there any more to that stacktrace?
h
Sorry about that 🙂 I'm just on my home now, will try to see if I can get more info out for you.
👍 1