#Next.js: How can I avoid sending a webhook POST request to a custom implementation?

9 messages · Page 1 of 1 (latest)

sharp tendon
#

How can I avoid sending a webhook POST request to a custom implementation, like Telegram, when the error priority is set to low in Sentry.io?

low oracle
#

how are you sending these requests?
Do you have a custom integration or an alert rule that sends alerts when the issue priority changes?

sharp tendon
#

I created a custom integration with Telegram and don’t want to send any requests when an issue or error set to low priority is created. But i don´t have this option...

low oracle
#

unfortunately that cannot be configured, if you set the "issue" field you will get webhook everytime a new issue is created and will have to filter the requests on the telegram side.
one workaround is to use the integration in an alert rule, where you can configure when the alert is triggered.

sharp tendon
#

Can I see any docs on how to do it?

sharp tendon
#

One thing that would be very useful would be if this webhook included the error priority configured in Sentry.io, but this information does not come in the body of the post request made to the webhook.

low oracle
#

the priority is not one of the available options at the moment, you can use the event level (only trigger if it has level error or fatal)

sharp tendon
#

Thank you for the docs! I really appreciate this!

Can I create an issue to implement priority as an attribute in the request body of the webhook call? If I do this, what is the probability of it being developed and merged?