removed restriction to allow alertmanager to work in all federation l…

…evels
labbsr0x · May 6, 2020 · 4fb621a · 4fb621a
1 parent 409b019
commit 4fb621a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -85,6 +85,7 @@ services:
       # - SCRAPE_PATHS=/your-custom-metrics-path
       # - SCHEME="https"
       - ALERT_MANAGER_URLS=alertmanager:9093
+      - ALERT_MANAGER_SCHEME=http
 
   bb-promster-2-l2:
     image: labbsr0x/bb-promster:latest

diff --git a/run.sh b/run.sh
@@ -78,15 +78,13 @@ if [[ "$CLEAR_RR" == "true" ]]; then
     rm /etc/prometheus/rules-ln.yml
 fi
 
-
 sed -i -e 's;$REMOTE_WRITE_URL;'"${REMOTE_WRITE_URL}"';g' "/prometheus.yml.tmpl";
 
-# the user can configure an alertmanager to manage alerts only on level 1 of the federation
 if [[ "$ALERT_RULES_FILE" == "" ]]; then
     export ALERT_RULES_FILE="/etc/prometheus/alert-rules.yml"
 fi
 
-if [[ "$ALERT_MANAGER_URLS" != "" -a "$BB_PROMSTER_LEVEL" == "1" ]]; then
+if [[ "$ALERT_MANAGER_URLS" != "" ]]; then
     sed -i -e 's;$ALERT_RULES_FILE;'"- $ALERT_RULES_FILE"';g' "/prometheus.yml.tmpl"
 
     cat >> "/prometheus.yml.tmpl" <<- EOM