Argo CD Integration
For GitOps teams, Argo CD is ground truth for what's actually running in production — not GitHub. Koalr integrates with Argo CD to receive real deployment events, not just CI build completions. This closes the gap that makes DORA metrics unreliable for GitOps orgs: Koalr counts syncs, not pushes.
What Koalr pulls from Argo CD
- Application sync events — Synced, Degraded, OutOfSync, and Progressing states
- Deployment timestamps per application per environment
- Health status history — Healthy, Progressing, Degraded, Missing, Suspended
- Diff detail — which manifest files changed in each sync
- Repository source and target revision per application
- Sync policy (automated vs. manual) and self-heal configuration
How Argo CD data feeds into Koalr
- DORA deployment frequency — Argo CD sync completions are ground-truth deploys for GitOps orgs
- Change failure rate — Degraded state within 10 minutes of sync = failure event
- Deploy risk outcome confirmation — Argo CD tells Koalr whether the predicted risk materialized
- Lead time for changes — commit-to-sync timeline for GitOps pipelines
- Multi-environment visibility — tracks promotions from staging to production
How to connect Argo CD
- 1
Go to Settings → Integrations in your Koalr dashboard.
- 2
Find Argo CD in the integrations list and click Connect.
- 3
Generate a read-only API token in Argo CD and paste it into Koalr. No OAuth flow required — the token is encrypted at rest.
- 4
Koalr begins syncing historical data immediately. Most integrations backfill 90 days of history on first connect.
Permissions and scopes requested
Koalr requests the minimum permissions required to read the data above. All access is read-only unless noted otherwise.
Argo CD API token (read-only, generated via argocd account generate-token)Koalr listens to Argo CD webhook notifications for real-time sync events
Ready to connect Argo CD?
Connect in under 5 minutes. Koalr backfills 90 days of history automatically — no manual imports, no CSV uploads.