---
title: "Audit what your clients send | Grafana Labs"
description: "Find high-cardinality log labels with logcli and enforce policy at a gateway"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## Audit what your clients send

Collectors and agents can attach dynamic labels you didn’t choose. Use the fewest labels test on whatever Alloy, Fluentd, or your Docker driver is applying. To see your streams and find high-cardinality labels, run:

Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```bash
logcli series '{}' --since=1h --analyze-labels
```

A label with thousands of unique values found in nearly every stream, such as a `requestId`, should be removed from labels and queried with a filter expression instead.

If many teams send logs and you can’t audit or change every client, apply the same approach you learned for metrics: route logs through gateway collectors your admin team owns, enforce label policy at that layer, and manage those gateway configurations centrally with [Fleet Management](/docs/grafana-cloud/send-data/fleet-management/).