[prometheus-users] Re: Alertmanager to send notifications to google chat

I can't speak for the project, but my guess would be it's out of scope. There are many existing integrations which use the existing webhook mechanism: https://prometheus.io/docs/operating/integrations/#alertmanager-webhook-receiver Doing it externally allows the request to be enriched with other

[prometheus-users] Re: Alertmanager to send notifications to google chat

Brian, thanks for pointing to other integrations. The reason why I was wondering about curling the messages is that the existing solution (Calert) provides little information about templating options. Alerts are incoming, but with tight information. I'd love to highlight severity in different

[prometheus-users] Re: Alertmanager to send notifications to google chat

If we're talking about the same "calert " then it looks like it already supports user-supplied templating of the message content: https://github.com/mr-karan/calert/blob/main/internal/providers/google_chat/message.go#L18-L53 The sample config shows how to

Re: [prometheus-users] Re: Remove labels in receiver Amazon SNS

> it doesn't show the expected result What result *does* it show, and how does it differ from what you expect? I suggest you first start by making a template that generates a dummy message, like "Hello". Once you know how to make your template replace the default one, then start adding to it

[prometheus-users] Re: Alertmanager to send notifications to google chat

> Invalid JSON payload received. Alertmanager's webhook sends a JSON message with a *fixed* payload format. See https://prometheus.io/docs/alerting/latest/configuration/#webhook_config *"The Alertmanager will send HTTP POST requests in the following JSON format to the configured endpoint"* You

[prometheus-users] Re: Alertmanager to send notifications to google chat

Thanks for reply Brian. I do realize, that Google Chat API requires a particular JSON format, but was assuming Alertmanager is capable of doing it by using particular template, which is wrong. Now the questions is whether it is worth creating a PR to create such a feature or it is out of