Infrastructure agent release notesRSS

Notes

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

Added

• The agent now adds Alibaba Cloud metadata, when available, to all data collected.
• When the agent runs in verbose mode, all integrations that support it now also run in verbose mode.
• When querying EC2 Instance Metadata Service the agent now uses Instance Metadata Service v2 (IMDSv2) for all requests. For more information on why you should use IMDSv2, see this AWS blog post .

Notes

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

Added

• The agent now logs error and fatal messages from integrations even when not running in verbose mode. This feature is only available to integrations configured using the V4 configuration format found in versions 1.8.0 or higher of the agent.

Fixed

• Fixed an issue where spaces in integration commands would sometimes get split incorrectly, causing the commands to fail.

Changed

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

Notes

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

Security fixes

• In Linux, at startup, the agent ensures it has ownership of the integrations temporary data folder, /tmp/nr-integrations/. This ensures only the agent/integrations can write into it negating potential abuse that could result in Denial/Degradation of Service.

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.