Alert thresholds depend on the nature of your applications. Some queries may have arbitrary tolerance thresholds. Building an efficient monitoring platform takes time. 😉
2 Prometheus alerting rules for ArgoCD. Exported via Embedded exporter. These rules cover critical and warning conditions — copy and paste the YAML into your Prometheus configuration.
groups:
- name: EmbeddedExporter
rules:
- alert: ArgoCDServiceNotSynced
expr: argocd_app_info{sync_status!="Synced"} != 0
for: 15m
labels:
severity: warning
annotations:
summary: ArgoCD service not synced (instance {{ $labels.instance }})
description: "Service {{ $labels.name }} run by argo is currently not in sync.\n VALUE = {{ $value }}\n LABELS = {{ $labels }}"
- alert: ArgoCDServiceUnhealthy
expr: argocd_app_info{health_status!="Healthy"} != 0
for: 15m
labels:
severity: warning
annotations:
summary: ArgoCD service unhealthy (instance {{ $labels.instance }})
description: "Service {{ $labels.name }} run by argo is currently not healthy.\n VALUE = {{ $value }}\n LABELS = {{ $labels }}" wget https://raw.githubusercontent.com/samber/awesome-prometheus-alerts/refs/heads/master/dist/rules/argocd/embedded-exporter.yml
Service {{ $labels.name }} run by argo is currently not in sync.
- alert: ArgoCDServiceNotSynced
expr: argocd_app_info{sync_status!="Synced"} != 0
for: 15m
labels:
severity: warning
annotations:
summary: ArgoCD service not synced (instance {{ $labels.instance }})
description: "Service {{ $labels.name }} run by argo is currently not in sync.\n VALUE = {{ $value }}\n LABELS = {{ $labels }}" Service {{ $labels.name }} run by argo is currently not healthy.
- alert: ArgoCDServiceUnhealthy
expr: argocd_app_info{health_status!="Healthy"} != 0
for: 15m
labels:
severity: warning
annotations:
summary: ArgoCD service unhealthy (instance {{ $labels.instance }})
description: "Service {{ $labels.name }} run by argo is currently not healthy.\n VALUE = {{ $value }}\n LABELS = {{ $labels }}"