# 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: 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-deployment/telemetry.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.