Guillaume Lefranc
Guillaume Lefranc
Yes they're quite consistent. What do you mean by evaluation interval? Is this tunable? Do you recommend to increase peer-timeout?
That just happens when starting alertmanager, no messages are appearing after this, those alertmanagers are deployed in the cloud and are pretty close to each other. Of note, we use...
We don't scrape those, I'll fix this and will look at metrics.
There's something wrong indeed, one node is ok, always sees the the other one the other AM sees its peer flapping all the time and cluster size going from 2...
OK, I found it, the 2nd node wasn't announcing itself on the correct address, it used Amazon internal IP instead of external :( it should work better now, of note...
The ping thingy doesn't seem to play well with Docker networks: ``` alertmanager_1 | level=debug ts=2018-09-18T12:52:01.276047845Z caller=cluster.go:287 component=cluster memberlist="2018/09/18 12:52:01 [WARN] memberlist: Got ping for unexpected node 01CQP8VVB33XSGRCWM3S7EJGN7 from=172.18.0.1:48699\n" ````...
OK, after changing it, we're still having duplicate issues for some reason they happen at larger intervals now. @mxinden the 1st machine is in AWS, the 2nd machine is at...
Yes, the metrics have been stable. What do you mean by notification payloads?
@mxinden do you mean the JSON payload? Unfortunately I am not sure how to access it. Is it logged anywhere? On the text side the outputs are strictly similar.
This is still an issue in 2019, can you let me know how to access the payloads?