Pushover notifications are broken about alertmanager HOT 10 CLOSED

@a86c6f7964 @antonlindstrom @Luzifer - you guys have been using Pushover in the past. Any clue about this problem?

from alertmanager.

I've used this successfully for quite some time and never seen an error like this. My best bet is that the clock is out of sync, that may cause some strange problems.

from alertmanager.

this is not a clock issue as confirmed by ntp.

from alertmanager.

I also have never seen this issue. Is it possible that the go library updated and alertmanager has not locked down the version?

from alertmanager.

That is possible. We don't vendor dependencies in alertmanager yet, but will do so at some point (we really should). If anyone is up for testing this against all current dependencies at that'd be awesome.

from alertmanager.

Can confirm the issue with my own builds. Currently having an open alert but no alert in pushover web console.

from alertmanager.

Does not look like an update in pushover lib… There is one change since 2014:
https://github.com/thorduri/pushover/compare/a8420a1935479cc266bda685cee558e86dad4b9f...master

This will not break anything… Maybe this is the problem: I'll take a look into the pushover API documentation.

from alertmanager.

To send an emergency-priority notification, the priority parameter must be set to 2 and the retry and expire parameters must be supplied.
(Source: https://pushover.net/api#priority)

So we need to send those two parameters too when sending emergency notifications. Seeing this the breaking change was 15 days ago with b7919b3.

from alertmanager.

Didn't notice there was a fix in #103, sorry. Filed #104 as an alternative though, it should be configurable IMO.

from alertmanager.

Closed #103 as #104 is a better solution!

from alertmanager.