Important
Agent Control and New Relic Control are now generally available for Kubernetes! Support for Linux hosts is also in public preview program, pursuant to our pre-release policies.
New Relic Control is an observability management solution that provides centralized, scalable control over agents and telemetry pipelines across your environment. This documentation covers the solution components, core functionality, and deployment options.
For a complete list of supported agents and their environments for Agent and Fleet Control, see our agent type compatibility documentation.
The public preview feature is provided pursuant to our pre-release policies.
New Relic Control is an observability management solution that provides centralized, scalable control over agents and telemetry pipelines across your environment. This documentation covers the solution components, core functionality, and deployment options.
Components
- Agent Control: A lightweight supervisor component that manages other New Relic and New Relic distribution of OpenTelemetry agents. It communicates with Fleet Control to remotely configure, update, and monitor the health of infrastructure-level instrumentation.
- Fleet Control: A centralized interface that provides visibility and remote management of all supervised agents across your infrastructure. It enables teams to install, configure, monitor, and upgrade agents at scale.
- Pipeline Control: The data management component of New Relic Control that helps filter and discard low-value data prior to database ingestion.
Scope
Agent Control and Fleet are in general availability (GA) for Kubernetes. At this stage, they support configuration management of infrastructure-level instrumentation for Kubernetes clusters, including:
- New Relic agents: Includes agents based on the New Relic infrastructure agent and the New Relic distribution of OpenTelemetry (NRDOT) collector.
- Standards-based instrumentation: Includes Prometheus and Fluent Bit.
Linux host environment support is in preview. Please see the documentation for Linux hosts for information on available features.
Pipeline Control is in general availability (GA) and can be used to manage data from APM agents by dropping low-value data. For details on supported agents, refer to Supported agent versions
Required permissions
- Agent Control: Requires the Authentication Domain Manager role to set up Agent Control and connect it to Fleet Control. For more information, refer to User Management Concepts.
- Fleet Control: Requires the Organization Manager role (referred to as Administrative setting in the product) to create and edit fleets within Fleet Control.
- Pipeline Control: Requires the Organization Manager role to set up and manage Pipeline Control gateway and Pipeline Control rules.