Pipeline Control Gateway release notesRSS

Configuration-only mode (without Flux)

• You can now install and operate Pipeline Control gateway without requiring Flux controllers in your cluster. In this mode, New Relic continues to manage your pipeline configuration (sampling, filtering, transforms) automatically through the UI, while you manage gateway infrastructure (scaling, versions) manually via Helm.
• This reduces the permissions footprint from cluster-admin to namespace-scoped ConfigMap access only, making it suitable for security-restricted and compliance-driven environments.
• A built-in config-watcher sidecar automatically detects configuration changes pushed from the UI and restarts gateway pods — no external operators (such as Stakater Reloader) required.
• For installation instructions, refer to Install gateway without Flux.

DaemonSet deployment mode

• Added support for deploying the gateway as a Kubernetes DaemonSet (one pod per node) instead of a Deployment with HPA. This is useful for environments that require node-level telemetry processing or consistent per-node resource allocation.
• Enable DaemonSet mode by setting daemonset.enabled: true in your Helm values. The DaemonSet mode also supports the config-watcher sidecar and customConfigMap for configuration-only installations.
• DaemonSet and Deployment modes are mutually exclusive — the chart uses conditional guards to ensure only one mode is active at a time.

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.

Pipeline Control gateway release notes - v2.0.1

Bug fixes

Fix for EU environment

Resolved an issue affecting Pipeline Control Gateway deployment and operation in EU environments. This fix ensures proper connectivity and data routing for EU-based instances.

Pipeline Control gateway release notes - v2.0.0

Updated to OpenTelemetry Collector v0.139.0

This release is based on OpenTelemetry Collector v0.139.0, bringing the latest stability improvements and features from the upstream project. This upgrade enables new data processing capabilities not available in previous gateway versions.

New processor capabilities

Added three new processors that give you control over your telemetry data before it leaves your infrastructure:

• Sampling processor: Reduce data volume with probabilistic and conditional sampling rules
• Filter processor: Drop entire records or specific attributes based on OTTL boolean conditions
• Transform processor: Add, modify, or delete attributes using OpenTelemetry Transformation Language (OTTL)

These processors can be chained together to create sophisticated data processing pipelines for metrics, events, logs, and traces.

Enhanced configuration options

• Redesigned UI: New form-based interface for creating and managing processor rules without writing YAML
• Enhanced YAML configuration: Support for OTTL-based processor configuration

Improved documentation structure

• Comprehensive guides for each processor type with OTTL examples and use cases
• Clear distinction between gateway rules (in your infrastructure) and cloud rules (in New Relic's infrastructure)
• Expanded troubleshooting resources for gateway installation, health monitoring, and data flow issues
• Reorganized information architecture for easier navigation

Pipeline Control Gateway Release Notes - v1.2.0

Upgrade OpenTelemetry Collector From 0.109.0 to 0.131.0

We have upgraded the internal OpenTelemetry Collector from version 0.109.0 to 0.131.0. This significant update includes numerous key improvements and bug fixes, providing a more robust and stable platform. For a complete list of changes, please refer to the OpenTelemetry Collector release notes.

Pipeline Control Gateway Release Notes - v1.1.0

Support for SQL trace and transaction trace data

• Implemented a new functionality to selectively drop data and attributes from SqlTrace and TransactionTrace events using drop rules.

Security updates

• Addressed vulnerabilities in the golang.org/x/net package, including a cross-site scripting issue and an HTTP Proxy bypass related to IPv6 Zone IDs.

• Upgraded to Go 1.24 and the following dependencies are updated to enhance security and incorporate recent fixes:

  • golang.org/x/net to v0.38.0
  • golang.org/x/sys to v0.31.0
  • golang.org/x/text to v0.23.0

Support for new functions

Added support for several new functions in NRQL drop rule queries. You can now use the following functions:

• aparse()
• floor()
• getField()
• hourOf()
• numeric()
• round()
• string()
• substring()
• weekdayOf()
• mod()
• dimensions()