ack_url_post and ack_url_get don't work

[iskhakov]

• check and fix ack_url_post and ack_url_get parameters
• add this feature to the documnetation and highlight in the interface

[Matvey-Kuk]

@iskhakov do we want to add them? Shouldn't it be a feature for a webhook?

[Matvey-Kuk]

ack_url_post and ack_url_get are optional payload paramethers which used to exist in the product before oficial release. I think we shouldn't bring this feature back because:

1. Processing payload paramethers without templating is breaking the concept of "render everything using Jinja" we have. Those paramethers were hardcoded which means if the payload source is not able to form the proper link, the user can't adjust it on the OnCall side.
2. It's making Webhooks feature not as straightforward. We have "Webhooks" page, it may be not easy to understand that some webhooks are generated because of "magic" paramethers in the alert payload.

What I suggest:

Think of some way to let users issue webhooks not only as an escalation step but also according to events which happened with Alert Group such as (New registered, new alert came, acked, resolved, snoosed), improve the page we have now:

[iskhakov]

Nice idea, I'm agree, we need to give the users ability to trigger outgoing webhooks based on the different events, such as incident acknowledged, incident resolved, also we can allow using outgoing webhooks in the personal notifications.

[Matvey-Kuk]

Personal notifications is a great idea! It will increase OnCall's applicability a lot.

[iskhakov]

we also need to

• add get method to the outgoing webhooks
• allow using json as a field (right now ninja converts it into string)

[tommysitehost]

This feature would be great. Would be good to be able to specify which alerts can trigger the webhook (e.g. alerts that have a specific label can trigger a webhook).

[iskhakov]

This functionality will be available in Outgoing Webhooks soon https://github.com/grafana/oncall/pull/1844