> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/investigate/traces-and-apm/application-performance-monitoring-apm/legacy-apm-metrics.md).

# Legacy APM Metrics

Legacy workload and resource golden-signal metrics are deprecated. Sensors no longer emit them by default. Prefer the [APM data source](https://docs.groundcover.com/investigate/querying-your-groundcover-data/explore-and-monitors-query-builder#apm) 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](https://docs.groundcover.com/investigate/querying-your-groundcover-data/explore-and-monitors-query-builder#apm). It exposes the same golden signals (requests, errors, error rate, request rate, and latency percentiles) against pre-aggregated APM measurements.

{% hint style="warning" %}
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.
{% endhint %}

### Enable legacy APM metrics

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

```yaml
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.

{% hint style="info" %}
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.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/investigate/traces-and-apm/application-performance-monitoring-apm/legacy-apm-metrics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.