Ctrlk
Log in|Playground
For the complete documentation index, see llms.txt. This page is also available as Markdown.

ArgoCD

Collect metrics from your ArgoCD components

groundcover supports metrics collection from your ArgoCD deployment, to allow you to visualize your continuous-delivery health and set up monitors.

Configuration is only enabled for Admins

How ArgoCD exposes metrics

ArgoCD is multi-component, and each long-running component exposes its own native Prometheus /metrics endpoint on a distinct port:

Component
Port

Application controller

8082

API server

8083

Repo server

8084

ApplicationSet controller

8080

Notifications controller

9001

Commit server

8087

These are the component metrics endpoints, not the argocd-server API. They are unauthenticated http in-cluster, so no credentials are needed in the common case. See ArgoCD's metrics documentation for details.

Adding the ArgoCD integration

Navigate to Data Sources and select ArgoCD.

Define the list of targets

ArgoCD is multi-endpoint: add one target per component you want to scrape. All targets share the same path and scheme:

  1. Scheme — http (the default for in-cluster component metrics endpoints).

  2. One or more endpoints — the component metrics services (e.g. argocd-metrics:8082, argocd-server-metrics:8083, argocd-repo-server:8084, argocd-applicationset-controller-metrics:8080).

  3. Path — /metrics.

  4. Authentication method — usually none; Basic Auth or a Bearer token only if you front the endpoints with an authenticating proxy.

Metrics scraping rules

On top of the targets configuration, you can also provide:

  1. Drop/Keep metrics (optional) — list of regexes of metrics to drop or keep.

    1. Drop metrics — drop all metrics that match any of the regular expressions.

    2. Keep metrics — drop all metrics that don't match any of the regular expressions.

  2. Additional relabeling (optional) — apply any additional Prometheus relabeling rules. Use the relabeling cookbook to configure them.

  3. Extra labels (optional) — a list of key-value pairs added to all scraped metrics from this configuration, such as env=production.

  4. Scrape interval and scrape timeout — control the cadence of scraping.

Scraping ArgoCD in-cluster (sensor / ServiceMonitor)

If groundcover runs in the same cluster as ArgoCD, you can also collect these metrics through the in-cluster scrape path instead of the tile: annotate the component metrics services with prometheus.io/scrape, or use the Prometheus-Operator ServiceMonitor manifests ArgoCD ships for each component. Either path keeps the metric names verbatim, so the same argocd_* series described below apply.

Common Questions

Where can I find scraped metrics?

All metrics in the platform can be found in the metrics exploration page: https://app.groundcover.com/explore/data-explorer.

For the full list of metrics groundcover collects from ArgoCD, what each means, and the labels you can slice by, see ArgoCD Metrics.

Last updated