> 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/customization/customize-usage/custom-labels-and-annotations/enrich-metrics-with-static-labels.md).

# Enrich data with static labels

groundcover allows you to add custom static key/value labels to all data ingested into your backend. This includes logs, traces, and metrics generated by the groundcover sensors, the k8s-watcher, and custom metrics scraped by the sensor.

For metrics, the static labels are added as metric labels. For logs, they appear in the Tags section. For traces, they are included as span attributes.

## Specifying what to collect

To apply custom static labels, you need to update your groundcover deployment `values.yaml` file.

The `global.labelEnrichment.staticLabels` configuration applies static labels to the telemetry as described above:

```yaml
global:
  labelEnrichment:
    staticLabels:
      environment: "production"
      team: "platform"
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/customization/customize-usage/custom-labels-and-annotations/enrich-metrics-with-static-labels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.