> 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/collect-data/customize-deployment/telemetry.md).

# Telemetry

As part of our offering, our services generate telemetry. This telemetry allows our support specialsts to provide assistance and solve problems, should you run into any.

It is widely recommended to keep telemetry flowing, but if you wish to stop it - the instructions are below.

## Overview

Partial telemetry is sent to our SaaS, for our support team to be able to get the big picture.

To enable or disable all telemetry, including SaaS-hosted telemetry:

{% tabs %}
{% tab title="Helm (k8s)" %}

```yaml
global:
  telemetry:
    enabled: true
```

{% endtab %}

{% tab title="Sensor (host)" %}

```yaml
telemetry:
  enabled: true
```

{% endtab %}
{% endtabs %}

## Drilldown

Full metrics telemetry is sent to the managed backend, for drilldowns. Metrics interval is relatively large, to provide insights while minimizing storage and compute overheads.

To configure backend-hosted telemetry:

{% tabs %}
{% tab title="Helm (k8s)" %}

```yaml
global:
  telemetry:
    metrics:
      localStorage:
        enabled: true
        interval: 5m
```

{% endtab %}

{% tab title="Sensor (host)" %}

```yaml
telemetry:
  metrics:
    localStorage:
      enabled: true
      interval: 5m
```

{% endtab %}
{% endtabs %}


---

# 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/collect-data/customize-deployment/telemetry.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.