ArgoCD Integration

Connecting ArgoCD lets Koalr track your GitOps deployment history — giving you accurate deployment frequency and MTTR metrics even when deployments are driven by ArgoCD syncs rather than traditional CI/CD pipelines.

Why this matters

~60% of enterprise Kubernetes teams use GitOps with ArgoCD. Without this integration, Koalr would see "build success" in GitHub Actions but miss the actual production deployment event — systematically undercounting deployments and making MTTR unmeasurable.

What Koalr syncs

• Application sync history — all ArgoCD syncs with timestamps, revisions, and triggering users
• Sync outcomes — Healthy vs. Degraded health status after each sync (maps to Deployment success/failure)
• Deployment frequency — feeds directly into DORA deployment frequency calculations
• MTTR signal — Degraded syncs followed by a recovery sync compute mean time to restore
• Change failure rate — proportion of syncs that resulted in Degraded health

Prerequisites

• ArgoCD v2.0 or later
• ArgoCD account with read access to applications
• Your ArgoCD server must be accessible from Koalr's servers (self-hosted ArgoCD behind a private network requires an outbound webhook proxy)

Setup

1. In Koalr, go to Integrations.
2. Click Connect next to ArgoCD.
3. Enter your ArgoCD server URL (e.g., https://argocd.your-company.com).
4. Enter your API token.
   • In ArgoCD UI: Settings → Accounts → [your account] → Generate Token
   • Required permissions: applications, get
5. Click Connect ArgoCD. Koalr validates the token and syncs the last 90 days of history immediately.

DORA dashboard

After connecting, ArgoCD deployment data appears in the DORA Metrics dashboard (/dora):

• Deployment frequency — ArgoCD syncs count as deployments, giving you an accurate daily/weekly cadence
• Change failure rate — ratio of Degraded-health syncs to total syncs
• MTTR — time from first Degraded sync to next Healthy sync for the same application
• Deployments list — individual sync events with revision SHA, application name, and health outcome

Troubleshooting

"Failed to authenticate" error: Ensure the server URL has no trailing slash and the API token hasn't expired. Tokens in ArgoCD are long-lived but can be manually revoked.

Only seeing some applications: ArgoCD's API returns only applications the token's account has access to. Ensure your ArgoCD account has applications, get permission for all projects you want tracked.

Deployments not appearing: After connecting, Koalr syncs history in the background. Wait 2–3 minutes, then refresh the DORA dashboard.