> 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/data-pipelines.md).

# Data Pipelines

groundcover provides powerful capabilities to manipulate incoming Telemetry in order to better serve your observability needs.

{% hint style="info" %}
Only admins can access and change the data pipelines rules
{% endhint %}

### Understanding Data Flow: Ingested → Filtered → Stored

When telemetry data flows through groundcover, it passes through three stages:

| Stage        | Description                                                              |
| ------------ | ------------------------------------------------------------------------ |
| **Ingested** | Data received by the groundcover backend from sensors or collectors      |
| **Filtered** | Data removed by pipeline rules (drop logs, filter traces) before storage |
| **Stored**   | Data persisted to storage after filtering                                |

You can monitor these stages using the [Ingestion data source](/investigate/querying-your-groundcover-data/explore-and-monitors-query-builder.md#ingestion) in the Data Explorer. This helps you track the effectiveness of your filtering rules and understand your storage volume.

{% hint style="info" %}
**Stored** metrics are currently available for **logs** and **traces** only. Metrics cardinality data is available on the [Metric Summary](/investigate/metrics/metric-summary.md) page.
{% endhint %}

### Pipeline Types

The following sub-pages explain each pipeline type:

* [Logs Pipeline](/collect-data/data-pipelines/log-pipelines.md)
* [Traces Pipeline](/collect-data/data-pipelines/traces-pipeline.md)
* [Metrics Aggregation](/collect-data/data-pipelines/metrics-aggregation.md)


---

# 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/data-pipelines.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.