---
title: pipeline-control-gateway-26-05-13
source: https://docs.newrelic.com/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-26-05-13
---

## Multi-fleet support

-   You can now create and manage multiple gateway fleets within a single organization. This allows separate business units or environments (for example, prod vs. staging) to maintain independent sampling, filtering, and transformation rules.
-   Easily navigate between different configurations using the new fleet selector dropdown in the Pipeline Control UI.

### Updated YAML schema

-   Migrated to a streamlined configuration that removes signal-specific nesting (for example, `logs:`, `spans:`) in favor of a direct rules array, making configurations flatter and easier to read.
-   For filter processors, the new schema supports an explicit `context` field. This enables more precise targeting of data sub-types, such as **metric datapoints** and **span events**.

### Improved deployment UX

-   The new deployment page now automatically fills in default values for the deployment name and description, significantly reducing the manual steps required to ship changes.
-   Added a side-by-side configuration diff preview for transform processors. This allows you to compare your new YAML logic against the current version before finalizing a deployment.