Por el momento, esta página sólo está disponible en inglés.

To overcome this, the goal is to eliminate blind spots with unified fleet governance, federated APM controls, and edge telemetry shaping. Agents are installed across thousands of hosts and services. Configurations drift over time. Teams adopt different standards. Telemetry volumes increase, and costs become harder to predict. What starts as a simple instrumentation effort quickly turns into a distributed systems problem of its own. Most organizations experience this shift gradually. 

By the time it becomes obvious, observability is already fragmented. Platform teams struggle to maintain consistent observability across heterogeneous estates, forcing them to manage Kubernetes, Host, and APM instrumentation with disjointed tools.

New Relic Control is designed to address that reality by giving teams a single, centralized control plane for managing observability pipelines and heterogeneous agents at scale.

The challenge: observability sprawl

As environments scale, observability does not fail loudly. It fails quietly. Agents run different versions across fleets. Configuration changes are applied inconsistently. DIY scripts and configuration management tools become brittle, operating as "fire and forget" mechanisms that lead to silent drift.

Meanwhile, platform teams become a bottleneck. The inability to safely delegate APM configuration permissions forces platform engineers to manually service every change request, creating a "ticket queue" that slows down innovation.

The symptoms are familiar:

  • Manual agent installs and upgrades across mixed environments.
  • Configuration drift that is difficult to detect or correct.
  • Platform teams burning cycles on manual updates instead of reliability engineering.
  • Rising telemetry costs from pure-play pipelines that manage data only after it leaves the agent.
  • Blind spots created by unmanaged or misconfigured instrumentation.

None of these problems are caused by a lack of observability tooling. They are caused by a lack of centralized control.

Why traditional approaches break down

Most observability platforms were built assuming instrumentation would be managed locally by individual teams or through static, brittle scripts. That model does not scale. As fleets grow larger and more distributed, relying on manual processes creates fragmentation. Even well-documented best practices erode over time as teams move faster and environments change.

Furthermore, introducing third-party "band-aid" pipeline tools adds complexity because they lack control over the agent itself. Without a unified control plane that manages both the source (the agent) and the stream (the pipeline), organizations are forced to choose between speed, consistency, and cost.

Enter New Relic Control

New Relic Control provides a unified way to manage agents, fleets, and telemetry pipelines from a single place.

It is designed to act as the governance layer for observability, allowing teams to centrally define, enforce, and evolve standards without slowing down delivery.

At its core, New Relic Control helps teams:

  • Automate the rollout, upgrade, and health monitoring of agents across Kubernetes (GA) and Host (Linux/Windows) environments.
  • Safely empower application teams to manage their own APM instrumentation.
  • Enforce role-based access control (RBAC), comprehensive audit logging, and automated drift detection.
  • Shape, sample, and route telemetry at the edge using a programmable pipeline gateway.

This is not about adding more tools. It is about managing observability intentionally.

Centralized fleet control for heterogeneous environments

Managing agents manually becomes a liability as environments grow. New Relic Control enables active state management, continuously monitoring fleet health and enforcing the desired state. It provides centralized lifecycle control for Kubernetes instrumentation and extends unified governance to Windows and Linux Host environments under a single policy model.

This reduces manual toil and helps ensure:

  • Agents remain up to date across all operating environments.
  • Enterprise-grade access controls and reliability standards are met.
  • Configuration changes are auditable and reversible.
  • Observability standards are enforced automatically.

Instead of relying on individual teams to maintain alignment, New Relic Control makes alignment the default.

Federated agility: Breaking the governance bottleneck

Standardization does not mean rigidity. It means creating guardrails that scale. Historically, platform teams could not safely delegate configuration to app teams without risking stability. New Relic Control introduces Federated APM Management, a delegated governance framework.

By utilizing granular role-based permissions, application owners can now safely tune their own APM instrumentation without breaking infrastructure-level guardrails. This removes the platform team bottleneck, accelerating innovation while maintaining strict compliance.

Telemetry shaping and cost optimization

As telemetry volumes grow, cost predictability becomes critical. Unchecked data volume erodes the ROI of observability. New Relic Control features an OTTL-powered Pipeline Control Gateway—a visual OpenTelemetry Transformation Language (OTTL) rules engine that allows teams to transform, filter, and manipulate telemetry data at the edge.

By managing telemetry upstream before it hits the platform, teams can:

  • Maximize data value with precision sampling and filtering.
  • Control spend more predictably.
  • Prioritize high-value signals.
  • Maintain consistent data quality.

This shifts cost management from reactive analysis to proactive control.

Designed for real-world operations

New Relic Control is built to integrate into existing environments and workflows.

It does not require teams to re-architect observability overnight. Instead, it provides a centralized layer that brings order to environments that have already grown complex. By unifying agent, fleet, and pipeline management, New Relic Control reduces operational overhead while ensuring 100% instrumentation coverage.