# Customize usage

[groundcover](https://www.groundcover.com) allows you to control the way data is being collected and treated across your cluster in many ways.

### Filtering Kubernetes entities

By default, groundcover traces all namespaces and workloads in your cluster, but sometimes you want to block ones that are irrelevant to your needs.

{% content-ref url="/pages/tlynEEX0sqcVxjTnGpOI" %}
[Filtering Kubernetes entities](/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage/filtering-kubernetes-entities.md)
{% endcontent-ref %}

### Customize retention

Strike the right balance between covering sufficient data for analysis and data storage.

{% content-ref url="/pages/kRNLW4fOqtFmBg7LyEWb" %}
[Custom data retention](/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage/custom-data-retention.md)
{% endcontent-ref %}

### Sensitive data obfuscation

Raw traces can go a long way in a troubleshooting process, but you can choose to obfuscate their payload.

{% content-ref url="/pages/siGmasqxyMZr08zCJ60U" %}
[Sensitive data obfuscation](/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage/sensitive-data-obfuscation.md)
{% endcontent-ref %}

### Customize Storage

Customize groundcover storage volumes for logs, metrics and traces.

{% content-ref url="/pages/JBrgYVsWkzkCJTwIJbWc" %}
[Custom storage](/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage/custom-storage.md)
{% endcontent-ref %}

### **Customize logs collection**

There are different methods that can allow you to filter the collection of logs based on your needs and/or only when issues related to these logs are identified.

{% content-ref url="/pages/e7XWbW3FBkQRnlwj5cgj" %}
[Custom logs collection](/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage/custom-logs-collection.md)
{% endcontent-ref %}

### **Customize tracing payload size**

Trace collection is driven by the payload size of a Span. You can customize the payload size limits to avoid truncation of the payload.

{% content-ref url="/pages/Rf99QUAm0lcIHdGo3awZ" %}
[Customize tracing payload size](/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage/customize-tracing-payload-size.md)
{% endcontent-ref %}

### **Disable tracing for specific protocols**

In certain situations it could be useful to disable the tracing of specific protocols. This modularity is natively supported by our sensor.

{% content-ref url="/pages/lsxoHap6trG8NiWMRtG4" %}
[Disable tracing for specific protocols](/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage/disable-tracing-for-specific-protocols.md)
{% endcontent-ref %}

### **Tuning resources**

In environments where the volume of transactions or operations per second is very high, resource tuning is essential to ensure that the cluster performs optimally.

{% content-ref url="/pages/8GBB14W7kGsxqFUVMbHE" %}
[Tuning resources](/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage/tuning-resources.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.groundcover.com/~/revisions/1mY0CQn12Klyi0QiItHv/customization/customize-usage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.