You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you do?
I'm deploying prometheus at k8s environment. two prometheus pods, point to two alertmanager pods, with mesh.peer point to each other.
Then I stopped a monitored service, got duplicate alert.
What did you expect to see?
deduplicate alert successfully
What did you see instead? Under which circumstances?
I stopped a monitered service with the command: # kubectl scale deploy spark-master-1 --replicas=0 -nkube-system
got two warning fires:
Environment
System information:
Linux 4.9.9-coreos-r1 x86_64
Prometheus version:
prometheus, version 1.7.1 (branch: master, revision: 3afb3ff)
build user: root@0aa1b7fc430d
build date: 20170612-11:44:05
go version: go1.8.3
Alertmanager version:
alertmanager, version 0.12.0 (branch: HEAD, revision: fc33cc78036f82ef8d4734c197a96f7cb6c952a3)
build user: root@c9169eb10d06
build date: 20171215-14:13:20
go version: go1.9.2
What did you do?
I'm deploying prometheus at k8s environment. two prometheus pods, point to two alertmanager pods, with mesh.peer point to each other.
Then I stopped a monitored service, got duplicate alert.
What did you expect to see?
deduplicate alert successfully
What did you see instead? Under which circumstances?
I stopped a monitered service with the command:
# kubectl scale deploy spark-master-1 --replicas=0 -nkube-system
got two warning fires:
Environment
System information:
Linux 4.9.9-coreos-r1 x86_64
Prometheus version:
prometheus, version 1.7.1 (branch: master, revision: 3afb3ff)
build user: root@0aa1b7fc430d
build date: 20170612-11:44:05
go version: go1.8.3
Alertmanager version:
alertmanager, version 0.12.0 (branch: HEAD, revision: fc33cc78036f82ef8d4734c197a96f7cb6c952a3)
build user: root@c9169eb10d06
build date: 20171215-14:13:20
go version: go1.9.2
Prometheus configuration file:
my local time is 8 hours behind the utc time.
The text was updated successfully, but these errors were encountered: