-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release the new Mimir Alertmanager #3752
Comments
Giantswarm installations deployment 🟠
Asked Panamax for object storage creation on |
Object storage configuration for panamax: https://github.com/giantswarm/panamax-configs/pull/56 Customer installations deployment 🟢
|
Parking this issue for a week before releasing this to customer installations. |
I checked manually OpsGenie and Slack and alerts are being received from giantswarm installations. |
Deployment is ok for customer installations Check list:
the script#!/bin/bash
source ~/projects/bash-magic/colors.sh
check_alertmanager() {
kubectl -n=mimir port-forward po/mimir-alertmanager-0 8080 1>/dev/null &
port_forward_pid=$!
trap "kill $port_forward_pid" EXIT
sleep 2
alertmanager_config_ok=false
if mimirtool alertmanager get --id anonymous --address http://localhost:8080|grep -q team_atlas_slack; then
alertmanager_config_ok=true
fi
alerts_present=false
if [ $(curl -SsH'X-Scope-OrgID: anonymous' localhost:8080/alertmanager/api/v2/alerts|jq -r '.|length') -gt 0 ]; then
alerts_present=true
fi
silences_present=false
if [ $(curl -SsH'X-Scope-OrgID: anonymous' localhost:8080/alertmanager/api/v2/silences|jq -r '.|length') -gt 0 ]; then
silences_present=true
fi
olly_ok=false
if kubectl -n=monitoring get deploy observability-operator -oyaml|grep -qE -- '- --alertmanager-enabled=true|- --alertmanager-secret-name=observability-operator-alertmanager|- --alertmanager-url=http://mimir-alertmanager-headless.mimir.svc:8080'; then
olly_ok=true
fi
mimir_ok=false
if helm -n=mimir get manifest mimir|grep -q 'alertmanager_url: dnssrvnoa+http://_http-metrics._tcp.mimir-alertmanager-headless.mimir.svc.cluster.local./alertmanager'; then
mimir_ok=true
fi
silence_operator_ok=false
if kubectl -n=monitoring get cm silence-operator -oyaml|grep -qE -- 'address: http://mimir-alertmanager-headless.mimir.svc:8080/alertmanager|tenantId: anonymous'; then
silence_operator_ok=true
fi
if $alertmanager_config_ok && $olly_ok && $mimir_ok && $silence_operator_ok && $alerts_present && $silences_present; then
echo -e "${GREEN}OK$NC"
else
echo -e "${RED}FAIL$NC"
fi
kill $port_forward_pid
}
list_capi_installation() {
opsctl list installations|grep -v 'giantswarm'|grep -E 'capa|capz|cloud-director|vsphere' |awk '{print $1}'
}
for i in $(list_capi_installation); do
echo "$i "
gx "$i" &>/dev/null
echo -n " verify: "
check_alertmanager
done |
Alerts are received on Slack (#alert) and OpsGenie |
Motivation
We know how to roll out the Mimir Alertmanager - now we need to announce and do it.
Todo
Check if customers have alerts in place (Dominik can help :))Outcome
We use the mimir alertmanager everywhere.
The text was updated successfully, but these errors were encountered: