Legacy APM Metrics

Legacy workload and resource golden-signal metrics are deprecated. Sensors no longer emit them by default. Prefer the APM data source for new monitors, dashboards, and Explore queries.

Use this page only if you still depend on the legacy Prometheus-style series (for example in Grafana alerts or dashboards) and need to keep emitting them.

Affected metrics

Workload metrics:

• groundcover_workload_total_counter

• groundcover_workload_error_counter

• groundcover_workload_issue_counter

• groundcover_workload_success_counter

• groundcover_workload_latency_seconds

Resource metrics:

• groundcover_resource_total_counter

• groundcover_resource_error_counter

• groundcover_resource_issue_counter

• groundcover_resource_success_counter

• groundcover_resource_latency_seconds

Other APM-related series (for example Kafka lag metrics) are unchanged.

Recommended migration

For native groundcover monitors, dashboards, and Explore, migrate queries to the APM data source. It exposes the same golden signals (requests, errors, error rate, request rate, and latency percentiles) against pre-aggregated APM measurements.

The APM data source is available in native groundcover only. It is not available in Grafana. If you still need equivalent Grafana alerts or dashboards, recreate them as native monitors/dashboards with the APM data source, or keep emitting the legacy metrics as described below.

Enable legacy APM metrics

To continue emitting the legacy series, set the following in your groundcover Helm values file and upgrade the deployment:

agent:
  sensor:
    enableLegacyApmMetrics: true

After the sensors restart with this setting, the legacy workload and resource metrics are emitted again and remain queryable from the Metrics data source and Grafana.

If you do not set this override, upgraded sensors stop sending these series. Existing monitors, dashboards, or Grafana alerts that still reference them will stop working as expected.