576fecf6d3
Related to https://github.com/grafana/irm/issues/332 (see https://github.com/grafana/oncall/pull/5440 and https://github.com/grafana/oncall/pull/5446 for the related UI changes) --------- Co-authored-by: Matt Thorning <matt.thorning@grafana.com>
1.6 KiB
1.6 KiB
| title | menuTitle | description | weight | keywords | canonical | aliases | refs | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Webhook as personal notification channel | Webhook | Learn more about using webhooks as a personal notification channel in Grafana OnCall. | 700 |
|
https://grafana.com/docs/oncall/latest/manage/notify/webhook/ |
|
|
Webhook as a personal notification channel
It is possible to setup a webhook as a personal notification channel in your user profile. The webhook will be triggered as a personal notification rule according to your notification policy configuration.
Configure a webhook to be used as personal notification
In the webhooks page, you (or a user with the right permissions) need to define a webhook as usual,
but with the Personal Notification trigger type.
Each user will then be able to choose a webhook (between those with the above trigger type) as a notification channel in
their profile. Optionally, they can also provide additional context data (as a JSON dict, e.g. {"user_ID": "some-id"})
which will be available when evaluating the webhook templates. This data can be referenced via {{ event.user.<key> }}
(e.g. {{ event.user.user_ID }}).