Use max instead of min

Since these services are replicated (two per service),
we should check for the max, not min, as one of the replicas
could be down, but still the API is Up.

Change-Id: I6dad9b74d65415f5f4f91e00c732792010487619
This commit is contained in:
Mateusz Matuszkowiak 2018-03-20 14:12:30 +01:00
parent be606a43c4
commit 53234ab0e5
3 changed files with 3 additions and 3 deletions

View file

@ -72,7 +72,7 @@
"tableColumn": "",
"targets": [
{
"expr": "min(up{job=\"alertmanager\"})",
"expr": "max(up{job=\"alertmanager\"})",
"format": "time_series",
"intervalFactor": 2,
"legendFormat": "",

View file

@ -72,7 +72,7 @@
"tableColumn": "",
"targets": [
{
"expr": "min(up{job=\"pushgateway\"})",
"expr": "max(up{job=\"pushgateway\"})",
"format": "time_series",
"intervalFactor": 2,
"legendFormat": "",

View file

@ -69,7 +69,7 @@
"tableColumn": "",
"targets": [
{
"expr": "min(up{job=\"remote_storage_adapter\"})",
"expr": "max(up{job=\"remote_storage_adapter\"})",
"format": "time_series",
"intervalFactor": 2,
"legendFormat": "",