Discussion: HA about consul-alerts HOT 10 CLOSED

How about letting each alert daemon run continuously, and periodically run leader election using Consul itself?

http://www.consul.io/docs/guides/leader-election.html

from consul-alerts.

Oh, I like that! :)

from consul-alerts.

Interesting. The client leader election looks pretty simple and cool.

At the moment, consul-alerts is already aware of which consul node is the leader though it does nothing with that info. Quick fix, It'd just be a simple change in the logic for enabling/disabling health checks (and a new config key) to enable this feature. This solves the immediate issue at hand though we're relying on consul's leader election instead of doing our own.

I do like the idea of consul-alerts having it's own leader-election.

from consul-alerts.

I do like the idea of consul-alerts having it's own leader-election.

Me too. I think it's a simple and robust idea.

from consul-alerts.

Using consul's build in leader election is the perfect way to handle this. Definitely on the right track here.

from consul-alerts.

Hi @darkcrux

I really don't want to push you, but do you know when you could release a new version with this patch?
Because I need it and so I have to know If I should implement something on my side to work-around this issue.

Thanks.

from consul-alerts.

@lyrixx I might have some time this week to hack around this. Aiming to complete this one and the reminder feature.

from consul-alerts.

Leader elections is now in place and is done automatically. Only the leader will send out notifications. Only works for checks and not events though as we may still want to trigger events on specific nodes.

from consul-alerts.

@darkcrux Thanks for this feature ;)

Could you release a new version? thanks.

from consul-alerts.

A new version has been released... can we close this issue?

from consul-alerts.