> 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/operate/customize-usage/customize-tracing-payload-size.md).

# Customize tracing payload size

In groundcover, trace spans are subject to a payload size limit. Any span with a payload larger than 10 KB (uncompressed) will be truncated.

The payload size limit applies separately to both the request and the response of the span. When comparing payload sizes, ensure that you know whether the value is reported as compressed or uncompressed. For example, a response of \~3 KB (compressed) might still exceed the 10 KB uncompressed limit and be truncated.

{% hint style="info" %}
**Note:** The groundcover UI displays the *wire size*, which is often smaller because of compression.
{% endhint %}

You can increase the limit by adjusting your values.yaml file. The value must be configured per protocol.

Example configuration:

```yaml
agent:
 sensor:
  httphandler:
   truncationConfig:
    payloadSizeLimit: 20480
```

### Supported Protocols

You can configure payload size limits for the following protocols:

* httphandler
* grpchandler
* redishandler
* sqlhandler
* mongodbhandler
* amqphandler


---

# 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/operate/customize-usage/customize-tracing-payload-size.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.