Infrastructure agent release notesRSS

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

• The Log Forwarder now adds additional validation and information logging when parsing the logging configuration files.
• Example configuration for the Log Forwarder has been added to the logging.d directory in the Infrastructure agent.
• When the Log Forwarder is started it will now only read YAML configuration files (*.yml and *.yaml).

For more information on the Log Forwarder, see Forward your logs using New Relic Infrastructure.

Fixed

• The Log Forwarder can now be started even if the hostname cannot be resolved.

Changed

• The built-in Flex integration has been updated to version 1.2.2. For more information, see the Flex changelog.
• Fluent Bit Output for New Relic has been increased to 1.2.1, see the changelog

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

• HTTP proxy support for the log forwarder. Log records are automatically sent through the same proxy used by the agent to send metrics.
• [BETA] HTTPS proxy support for the log forwarder.

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

• Agent version is now logged in non-verbose mode, too.

Fixed

• A missing parsers configuration file for the log forwarder has been restored to the Windows installer.
• The mountInfo / diskstats mapping for fetching LVM volumes' I/O stats has been fixed; it can still fail for older systems that lack a mountInfo file and use custom names for their LVM volumes.
• A bug in the log forwarder that prevented some tcp and syslog URIs to be parsed correctly has been fixed.

Changed

• The built-in Flex integration has been updated to version 1.1.2. For more information, see the Flex changelog.
• The built-in Docker integration has been updated to version 1.2.1. For more information, see the Docker integration changelog.

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

• Integrations can now be enabled or disabled via environment variables. This feature is only valid from version 1.8.0, since it requires the V4 configuration format.

Example:

integrations:
  - name: my-integration
    when:
      env_exists:
        MY_ENV_VAR: true
    interval: 15s

Changed

• Improvements in the agent internals to better support ECS environments.

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

• [Beta] Log forwarding can now collect Syslog logs.
• [Beta] Log forwarding can now collect logs over plain TCP socket connections.
• [Beta] Log forwarding can now be configured via user-provided Fluent-Bit configuration files.
• [Beta] Log forwarding is now able to include custom attributes for each log record as key-value pairs.

For more information, see Forward your logs using New Relic Infrastructure.

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

• The agent can now retrieve secrets from Vault when running KV Secrets Engine - Version 1.
• Log forwarder entries now include hostname as an attribute.

Changed

• Update nri-docker to v1.2.0 (beta Fargate)

Security fixes

• Fixed an issue that could cause secrets to leak into log warning messages when using secrets management.

Bug fixes

• Fixed a log forwarder error that occurred when enabling eventlog sources.
• Fixed an issue that could cause the storage sampler to not return all mount points for a device.
• Avoid spamming the log when agent can't get a process path. This happened mostly when dealing with Windows system-level processes.

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

Beta: Log forwarding allows you to forward logs to New Relic using the infrastructure agent. For more information, see Forward your logs using the New Relic infrastructure agent.

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

• The agent now includes the AWS region in the inventory data under metadata/system when running in an AWS VM.

Bug fixes

• Fixed bug on Debian 7 and Centos 5 where the agent would leave child processes running after receiving a service management stop instruction.

Notes

A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.

Added

• Samplers that are disabled are no longer pre-warmed avoiding errors messages in the log.

Bug fixes

• Fixed an issue with the containerized agent where the agent would crash when the container is stopped
• Fixed an issue in Linux where in some situations the process display name would be empty
• Fixed an issue where in certain situations the unavailability of cpu metrics would lead to a crash