# Disable tracing for specific protocols

By default, groundcover automatically collects traces and metrics for all supported protocols, in order to generate the most comprehensive picture possible. However, in certain situations it could be useful to disable the tracing of specific protocols. This modularity is natively supported by our sensor, and this section will describe how to do so.

### Disabling protocols

In order to stop the collection of a specific protocol - say, HTTP - add the following lines to the groundcover deployment values file:

```yaml
agent:
  sensor:
    env:
    - name: FLORA_NETWORKTRACER_CONNECTIONMANAGER_PROTOCOLS_HTTP_ENABLED
      value: "false"
```

In order to disable multiple protocols, simply add another env variable. If we want to disable both HTTP and Redis, for example:

```yaml
agent:
  sensor:
    env:
    - name: FLORA_NETWORKTRACER_CONNECTIONMANAGER_PROTOCOLS_HTTP_ENABLED
      value: "false"
    - name: FLORA_NETWORKTRACER_CONNECTIONMANAGER_PROTOCOLS_REDIS_ENABLED
      value: "false"
```

**The list of supported protocols:**

* HTTP
* HTTP2 (will also disable gRPC)
* REDIS
* DNS
* POSTGRESQL
* MYSQL
* KAFKA
* MONGODB


---

# 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/customization/customize-usage/disable-tracing-for-specific-protocols.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.