--- title: Modify agent configuration source: https://docs.newrelic.com/docs/new-relic-control/pipeline-control/gateway/modify-agent-configuration --- For the gateway to process your agents' telemetry data, reconfigure them to route data to your gateway cluster instead of directly to New Relic. How you do that depends on the agent type: New Relic APM agents use `NEW_RELIC_HOST`, OpenTelemetry sources use OTLP exporter settings, and log forwarders use their own output plugin configuration. The sections below cover each agent type. All examples use the cluster-local gateway endpoint. Replace it with your actual endpoint if agents run outside the cluster. ## New Relic APM agents `NEW_RELIC_HOST` is APM-only and has no effect on OpenTelemetry sources, the Infrastructure agent, or log forwarders. The gateway endpoint must be reachable over HTTPS, so APM agents connect through the in-cluster reverse proxy (NGINX or Kong) or the out-of-cluster ALB, not directly to the gateway pod. The following example shows a Node.js agent configuration file: ```js 'use strict' /** * New Relic agent configuration. * * See lib/config/default.js in the agent distribution for a more complete * description of configuration variables and their potential values. */ exports.config = { /** * Array of application names. */ app_name: ['My Application'], /** * Your New Relic Host endpoint. */ NEW_RELIC_HOST: 'GATEWAY_DNS_ENDPOINT_HERE', /** * Your New Relic license key. */ license_key: 'license key here', logging: { /** * Level at which to log. 'trace' is most useful to New Relic when diagnosing * issues with the agent, 'info' and higher will impose the least overhead on * production applications. */ level: 'info' }, /** * When true, all request headers except for those listed in attributes.exclude * will be captured for all traces, unless otherwise specified in a destination's * attributes include/exclude lists. */ allow_all_headers: true, attributes: { /** * Prefix of attributes to exclude from all destinations. Allows * as wildcard * at end. * * NOTE: If excluding headers, they must be in camelCase form to be filtered. * * @name NEW_RELIC_ATTRIBUTES_EXCLUDE */ exclude: [ 'request.headers.cookie', 'request.headers.authorization', 'request.headers.proxyAuthorization', 'request.headers.setCookie*', 'request.headers.x*', 'response.headers.cookie', 'response.headers.authorization', 'response.headers.proxyAuthorization', 'response.headers.setCookie*', 'response.headers.x*' ] } } ``` /\* \[NEW SECTION START] \*/ ## OpenTelemetry Collector **Minimum version:** opentelemetry-collector-contrib v0.104.0 Use the `otlphttp` exporter pointed at the gateway's OTLP HTTP port. Deploy this configuration as a Kubernetes ConfigMap: ```yaml exporters: otlphttp: endpoint: http://pipeline-control-gateway.newrelic.svc.cluster.local:4318 tls: insecure: true service: pipelines: traces: exporters: [otlphttp] metrics: exporters: [otlphttp] logs: exporters: [otlphttp] ``` > #### ⚠️ IMPORTANT > > Use the `otlphttp` exporter, not `otlp`. The Helm chart renames `otlp` to `otlp_grpc` internally, which is invalid for this collector version. ## eBPF auto-attach agent Configure the eBPF APM auto-attach agent to send telemetry via OTLP gRPC by setting `customOtlpEndpoint` in your values file: ```yaml customOtlpEndpoint: "pipeline-control-gateway.newrelic.svc.cluster.local:4317" customOtlpEndpointTlsEnabled: false reportLogs: "true" ``` This routes both metrics and logs through the gateway's OTLP gRPC receiver on port 4317. TLS is disabled because the connection stays within the cluster. ## Infrastructure agent **Minimum version:** v1.62.0 The Infrastructure agent has two separate configuration paths depending on what you want to route through the gateway: - **All telemetry (metrics, events, inventory, and logs):** Use `collector_url` and `metric_url` in your Helm values. This routes everything the agent collects through the gateway. - **Logs only:** Use `logging_endpoint` in `newrelic-infra.yml`. This routes only log forwarding through the gateway while other telemetry continues to go directly to New Relic. ### Route all telemetry through the gateway Set `collector_url` and `metric_url` in your Helm values: ```yaml newrelic-infrastructure: common: agentConfig: collector_url: "http://pipeline-control-gateway.newrelic.svc.cluster.local" metric_url: "http://pipeline-control-gateway.newrelic.svc.cluster.local" ``` ### Route logs only through the gateway Set `logging_endpoint` in `/etc/newrelic-infra.yml` and enable log forwarding: ```yaml license_key: YOUR_LICENSE_KEY logging_endpoint: http://pipeline-control-gateway.newrelic.svc.cluster.local/log/v1 log: forward: true ``` Use `http://` for the cluster-local endpoint. Use `https://` only when routing through an in-cluster reverse proxy (NGINX or Kong) with cert-manager deployed. Then define which log files to forward in `/etc/newrelic-infra/logging.d/logging.yml`: ```yaml logs: - name: my-app-logs file: /var/log/my-app.log ``` Restart the Infrastructure agent to apply the changes. /\* \[NEW SECTION END] \*/ ## Compatibility matrix: Supported agents and versions The following table lists the New Relic APM agents, Infrastructure agents, and log collectors supported for use with the gateway. Note that support for the Gateway feature doesn't override the general [New Relic end-of-life (EOL) policies](https://docs.newrelic.com/docs/licenses/end-of-life/notification-changes-new-relic-saas-features-distributed-software/) or any applicable [agent-specific EOL policies.](https://docs.newrelic.com/docs/licenses/end-of-life/notification-changes-new-relic-saas-features-distributed-software/#eol-agents). | Agent type/Language | Versions available | | ---------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | | New Relic APM agents | See language-specific versions below: | |     [.NET](https://docs.newrelic.com/docs/apm/agents/net-agent/configuration/net-agent-configuration/) | 8.17.438 and later | |     [Go](https://docs.newrelic.com/docs/apm/agents/go-agent/configuration/go-agent-configuration/) | 2.2.0 and later | |     [Java](https://docs.newrelic.com/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/) | 4.9.0 and later | |     [NodeJS](https://docs.newrelic.com/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/) | 6.10.0 and later | |     [PHP](https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/) | 10.0.0 and later | |     [Python](https://docs.newrelic.com/docs/apm/agents/python-agent/configuration/python-agent-configuration/) | 4.10.0 and later | |     [Ruby](https://docs.newrelic.com/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration/) | 6.1.0 and later | | [Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview) | 1.62.0 and later | | [Kubernetes agent](/install/kubernetes) | v3.33.2 and later | | [Fluent Bit agent](https://docs.newrelic.com/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding) | 2.3.0 and later | | [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) | opentelemetry-collector-contrib v0.104.0 and later | | [MELT APIs](https://docs.newrelic.com/docs/apis/intro-apis/introduction-new-relic-apis/#data-type-apis) | NA | The versions listed are representative of the range available for each language. For detailed version information, refer to the specific agent documentation. ## Next topic - [Understand your ingest pipeline](https://docs.newrelic.com/docs/new-relic-control/pipeline-control/ingest-pipeline)