A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1.
Changed
- Updated the Go version to 1.25.7
Security
- Addresses vulnerabilities
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1.
Changed
- Updated dependency newrelic/nri-prometheus to v2.27.6 in #2177
- Updated dependency newrelic/nri-flex to v1.17.3 in #2180
- Updated dependency newrelic/nri-winservices to v1.4.2 in #2181
- Updated dependency newrelic/nri-docker to v2.6.7 in #2182
- Updated the go version to 1.25.6 in #2183
Security
- Addressed High Vulnerabilities CVE-2025-61726 and CVE-2025-61728
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1.
Added
- Added
logging_http_client_timeoutconfiguration option to control HTTP client timeout (in seconds) for the New Relic fluent-bit output plugin in #2167 - Added upload schema for RHEL10 in #2171
Changed
- Make
win_network_interface_v2flag true by default in #2173 - Updated min version for pkg-tests in #2172
Security
- Addressed Critical Vulnerability - CVE-2025-15467 and High Vulnerability - CVE-2025-69419
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1.
Added
- Added support for RHEL10 in #2169
Changed
- Updated newrelic_plugin_version in #2170
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1.
Fixed
Fixed
transmitBytesPerSecondshowing zero during high traffic on Windows (NR-502872) in #2166Important
To enable this fix, you must set the
win_network_interface_v2configuration option totrue. This option uses 64-bit counters instead of 32-bit counters for network metrics on Windows.
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1.
Changed
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0.
Security
A new version of the Fluent Bit version has been released with a fix for CVE-2025-12972, CVE-2025-12970,CVE-2025-12978,CVE-2025-12977,CVE-2025-12969 . Fluent Bit versions earlier than v4.0.13 series are affected by security vulnerabilities. The specific plugins and their associated vulnerabilities are following:
- Forward input plugin (in_forward) - Affected by CVE-2025-12969
- Docker input plugin (in_docker) - Affected by CVE-2025-12970
- File output plugin (out_file) - Affected by CVE-2025-12972
- HTTP, Splunk, and Elasticsearch input plugins (in_http, in_splunk, in_elasticsearch) - Affected by CVE-2025-12978 & CVE-2025-12977
Notes:
- There is no secure FluentBit upstream package available for Ubuntu 16, 18, and 20. If you are running on any of these distributions, make sure you remove the affected input plugins to protect from vulnerabilities.
- We are working to provide secure packages for SLES 12.5 and 15.4 as soon as possible. Until we roll out the safe packages for these distributions, we recommend removing the affected plugins to protect from vulnerabilities.
- We are working to provide a secure package for Debian 10 as soon as possible. Until we roll out a safe package for this distribution, we recommend removing the affected plugins to protect from vulnerabilities.
Changed
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0.
Changed
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0.
Changed
A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.0.
Changed
feat(oci): add Oracle Cloud-specific tags to hosts running on OCI in https://github.com/newrelic/infrastructure-agent/pull/2121
Starting with version 1.70.0, the New Relic Infrastructure agent now automatically collects metadata for VMs running in Oracle Cloud Infrastructure (OCI). The agent collects the following details:
- displayName
- host.id
- oci.availabilityDomain
- oci.region
- oci.compartmentId
- oci.shape
- oci.imageId
You can use this metadata as tags for entity search or as attributes in NRQL queries. The
host.idattribute is also used by the New Relic Cloud Integration for OCI to attach cloud metadata to the correct host entity.This feature is enabled by default to ensure consistency with existing metadata on other cloud providers. If you need to disable this feature, you can use the configuration settings disable_cloud_metadata or disable_cloud_instance_id.
Background: For many years already, New Relic Infrastructure Agents installed on a VM running in AWS, Azure or GCP had the equivalent metadata detail collection, and this behavior is enabled by default. For consistency across different clouds, the OCI feature is using the same configuration items and the same default behavior.