I created a firing alert and configured an alert manager config to route alerts to Victorops with the Victorops config field message_type = warning. I am using the Victorops REST API integration.
What did you expect to see?
I expected to see the message come through to VictorOps with message_type = warning.
What did you see instead? Under which circumstances?
Instead, the message came through to VictorOps with message_type = CRITICAL.
This was an issue with the kube prometheus stack's default rules using lowercase severity values instead of uppercase, AM appears to ignore the value 'warning', instead 'WARNING' must be used.
What did you do?
I created a firing alert and configured an alert manager config to route alerts to Victorops with the Victorops config field message_type = warning. I am using the Victorops REST API integration.
What did you expect to see?
I expected to see the message come through to VictorOps with message_type = warning.
What did you see instead? Under which circumstances?
Instead, the message came through to VictorOps with message_type = CRITICAL.
Environment
System information:
insert output of
uname -srm
hereAlertmanager version:
0.25.0
Prometheus version:
0.42.0
Alertmanager configuration file:
source_matchers:
source_matchers:
source_matchers:
name: "null"
name: observability/alertmanager-procurement-config/procure-dev-receiver victorops_configs:
/etc/alertmanager/config/*.tmpl
Prometheus configuration file:
/etc/prometheus/rules/prometheus-prometheus-operator-promet-prometheus-rulefiles-0/*.yaml scrape_configs:
job_name: serviceMonitor/observability/prometheus-operator-promet-kube-etcd/0 honor_timestamps: true scrape_interval: 30s scrape_timeout: 10s metrics_path: /metrics scheme: http authorization: type: Bearer credentials_file: /var/run/secrets/kubernetes.io/serviceaccount/token follow_redirects: true enable_http2: true relabel_configs:
Logs: n/a