Alertmanager fingerprints not sent to receivers

485 views
Skip to first unread message

dpetit...@gmail.com

unread,
Aug 1, 2018, 5:49:29 PM8/1/18
to Prometheus Users
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

femina josephine

unread,
Aug 2, 2018, 1:27:23 AM8/2/18
to Prometheus Users
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.

Simon Pasquier

unread,
Aug 2, 2018, 3:57:05 AM8/2/18
to femina josephine, Prometheus Users
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.

--
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.

For more options, visit https://groups.google.com/d/optout.

Brian Brazil

unread,
Aug 2, 2018, 4:11:14 AM8/2/18
to Simon Pasquier, femina josephine, Prometheus Users
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-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.

For more options, visit https://groups.google.com/d/optout.

--
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.

For more options, visit https://groups.google.com/d/optout.



--

dpetit...@gmail.com

unread,
Aug 2, 2018, 8:21:51 AM8/2/18
to Prometheus Users
Thank you both for your answers. If I understand correctly, it seems from Brian's response that adding the fingerprint field to the webhook data would not negatively impact existing users, apart from the extra bandwidth it incurs.

In your opinion, is adding the fingerprint something that would have enough value to justify a change, or should I stick with Simon's proposal of generating the fingerprint from the labels?

Cheers,
Danny


On Thursday, 2 August 2018 04:11:14 UTC-4, Brian Brazil wrote:
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.

--
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.



--
Reply all
Reply to author
Forward
0 new messages