Skip to main content
For Deployments that use git-sync to deploy Dags, the git-sync relay emits operational metrics through StatsD. These metrics provide visibility into sync operations, repository size, and sync performance for each Deployment. Git-sync relay metrics are disabled by default and require configuration at both the platform and cluster levels.
In APC 2.0, the strict schema validator doesn’t recognize git-sync relay metrics. You must disable the strict schema check to use this feature. See the following configuration steps.

Prerequisites

  • Astro Private Cloud 2.0 or later with Helm chart version 2.0.0 or later.
  • System Admin access to update the Astro Private Cloud Helm configuration.
  • One or more Deployments configured to use git-sync for Dag deployment.

Enable git-sync relay metrics

1

Disable the strict schema check

Because the strict schema validator in APC 2.0 doesn’t recognize git-sync relay metrics fields, you must disable it. Add the following to your platform-level values.yaml:
2

Enable metrics at the platform level

In the same platform-level values.yaml, enable git-sync relay metrics globally:
3

Enable metrics in the cluster configuration

In your cluster configuration, enable git-sync relay metrics:
4

Apply the configuration

Run a Helm upgrade to apply the changes:
5

Verify the metrics

After a successful Helm upgrade, git-sync relay metrics are available through the Deployment’s StatsD exporter. Run the following command to confirm metrics are being emitted:

Available metrics

The following metrics are available with the git_sync_relay_ prefix. All metrics are emitted per Deployment.

Sync operation metrics

Git operation metrics

File and repository metrics

Initialization metrics

State metrics