---
title: "Pipeline"
description: "Decide which telemetry to keep and where: OTel-native filters in the collector, ingestion control at the edge, and backend filters before storage."
section: "Pipeline"
breadcrumb: "Pipeline > Pipeline Features"
canonical: "https://docs.middleware.io/features/pipeline"
---
# Pipeline

Pipeline lets you decide what telemetry is worth keeping, and where that decision happens. Otel-native filters run in the cluster's OpenTelemetry Collector to drop, rename or compact attributes before data leaves the node; Ingestion control shapes what is accepted as it reaches Middleware; and Backend data filters drop matching spans, logs or metrics right before storage, permanently. Rules are built in a visual pipeline graph, one per layer, so trimming noise or cost is a config change rather than a redeploy of every agent.

## Features

- [Overview](/features/pipeline/setup) — See how telemetry flows from source to storage
- [Configure Backend Data](/features/pipeline/backend-control) — Drop matching spans, logs or metrics right before storage
- [Otel-native filters](/features/pipeline/otel-filters) — Trim or rename attributes inside the cluster collector
- [Ingestion control](/features/pipeline/ingestion-control) — Decide what is accepted as data reaches Middleware

## Related Features

- [Logs Management](/features/logs) — Search, filter and turn log patterns into metric
- [Infrastructure](/features/infrastructure) — Hosts, Containers, Kubernetes etc.
- [Dashboards](/features/dashboards) — Visualise telemetry data
- [Alerts](/features/alerts) — Create alert rules and service level objectives