--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscribe@googlegroups.com.
To post to this group, send email to prometheus-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/19a66eae-c2f1-405b-b178-c0b73c816fbd%40googlegroups.com.
The fingerprint is computed from the alert's labels so the webhook endpoint can recompute it if needed.Changing the webhook data format can impact existing users so it's not free either.
--On Thu, Aug 2, 2018 at 7:27 AM, femina josephine <femina.j...@gmail.com> wrote:This was the same query i asked and did not receive any reply. Kindly let me know if you know any solution. Work around is really difficult. It would be great if fingerprint is sent as part of HTTP POST to the webhooks.--
On Thursday, 2 August 2018 03:19:29 UTC+5:30, dpetit...@gmail.com wrote:Hi,I'm looking to leverage Alertmanager's functionalities for one of our internal applications, and I'm specifically interested in the webhook receiver to listen for firing and resolved alerts.I'm interested in getting the unique fingerprint associated with the alert, however I noticed that it is not sent as part of the HTTP POST request as per the config documentation. However, the fingerprint is returned by querying the /api/v1/alerts endpoint, as per this comment. Is there a reason why the fingerprint is not included in the webhook response?I'll gladly submit a pull request if fingerprints can be added to the webhook response message.Cheers,Danny
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscribe@googlegroups.com.
To post to this group, send email to prometheus-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/19a66eae-c2f1-405b-b178-c0b73c816fbd%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscribe@googlegroups.com.
To post to this group, send email to prometheus-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAM6RFu4Lzz9JaLxVBHyQamjLovRdMgxhkGB3TPKKz7N7J%2Bd3Cg%40mail.gmail.com.
On 2 August 2018 at 08:57, Simon Pasquier <spas...@redhat.com> wrote:The fingerprint is computed from the alert's labels so the webhook endpoint can recompute it if needed.Changing the webhook data format can impact existing users so it's not free either.Adding fields is okay, the only impact is the extra bandwidth. Changing fields is not okay.Brian
On Thu, Aug 2, 2018 at 7:27 AM, femina josephine <femina.j...@gmail.com> wrote:
This was the same query i asked and did not receive any reply. Kindly let me know if you know any solution. Work around is really difficult. It would be great if fingerprint is sent as part of HTTP POST to the webhooks.
On Thursday, 2 August 2018 03:19:29 UTC+5:30, dpetit...@gmail.com wrote:Hi,I'm looking to leverage Alertmanager's functionalities for one of our internal applications, and I'm specifically interested in the webhook receiver to listen for firing and resolved alerts.I'm interested in getting the unique fingerprint associated with the alert, however I noticed that it is not sent as part of the HTTP POST request as per the config documentation. However, the fingerprint is returned by querying the /api/v1/alerts endpoint, as per this comment. Is there a reason why the fingerprint is not included in the webhook response?I'll gladly submit a pull request if fingerprints can be added to the webhook response message.Cheers,Danny
--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/19a66eae-c2f1-405b-b178-c0b73c816fbd%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAM6RFu4Lzz9JaLxVBHyQamjLovRdMgxhkGB3TPKKz7N7J%2Bd3Cg%40mail.gmail.com.