Infrastructure agent release notes

Tuesday, June 2, 2020 - 12:30

Notes

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

Added

For more information on the log forwarder feature, see Forward your logs using New Relic Infrastructure.

Changed

Monday, May 25, 2020 - 12:30

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 .
Thursday, May 21, 2020 - 10:30

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

Friday, May 8, 2020 - 12:00

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.
Thursday, May 7, 2020 - 12:00

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

Wednesday, April 29, 2020 - 11:00

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.
Monday, April 20, 2020 - 17:00

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

Tuesday, April 14, 2020 - 17:00

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.
Wednesday, April 8, 2020 - 17:00

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.

Wednesday, April 1, 2020 - 10:00

Notes

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

Added

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.
Monday, March 23, 2020 - 10:00

Notes

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

Added

Friday, March 20, 2020 - 12:00

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.
Tuesday, March 17, 2020 - 12:00

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
Tuesday, March 10, 2020 - 12:00

Notes

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

Added

  • Improved auto discovery of ports:
    • If a container exposes ports 80 and 443, then ${discovery.port} or ${discovery.ports.0} would equal to port 80 and ${discovery.ports.1} to 443. As ports are are sorted in ascending order, port 8080 would have been assigned to number three and so on.
    • Ports are also tagged by port type (usually TCP): ${discovery.ports.tcp} and ${discovery.ports.tcp.0} would equal to 80 and ${discovery.ports.tcp.1} to 443.

Bug fixes

  • On Windows, the agent can now report processes even when their command line cannot be gathered. The commandLine attribute will be empty in those cases.
Thursday, February 27, 2020 - 12:00

Notes

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

Added

  • The agent now sends the integration name (integrationName) and version (integrationVersion) when any events are generated.
    • For example, when using the Redis monitoring integration integrationName will be set to com.newrelic.redis and integrationVersion to 1.4.0
  • nri-flex has been upgraded to version v1.0.0.
  • RPM packages generated now include the distribution name in the filename. For example:
    • The RHEL8 package newrelic-infra-<version>-1.x86_64.rpm will now become newrelic-infra-<version>-1.el8.x86_64.rpm when published.

Bug fixes

  • The agent no longer panics on startup when reading corrupt caches files.
  • When using new configuration format the agent would create inventory as integration/<binary name> rather than integration/<integration name> breaking some charts. For better backwards compatibility the agent will now create inventory using the integration's name.
    • For example, when using the Redis monitoring integration before it would create inventory under integration/nri-redis but with the new update it will create it under inventory/com.newrelic.redis
  • Sample text fields are now truncated to 4095 characters. Before these fields would be rejected and so would never appear in New Relic. Now the fields will appear but will be truncated.
Tuesday, February 18, 2020 - 15:00

Notes

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

Added

Bug fixes

  • Auto-discovery annotations no longer override integration metrics.
    • For example: it avoids Kubernetes auto-discovery overriding the cluster_name attributes if it's already set in the integration configuration.
  • Removed a memory leak that caused a slow but constant increase in memory and CPU consumption (up to 1%cpu & 5MB per week).
Monday, February 10, 2020 - 15:00

Notes

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

Bug fixes

  • Updated bundled nri-docker integration version to v1.1.1.
    • This version fixes missing Docker container metrics improving Linux cgroup path detection. This issue happened when cgroup was not mounted in the standard path /sys/fs/cgroup. Now it can discover different cgroup paths.
    • Still cgroup PIDs (process and thread count) is not available on Kernel versions lower than 4.3 see support. Therefore column threadCount won't be available for these systems. For instance Amazon-Linux v1 runs on kernel 4.13.
  • Fixed permissions to /tmp/nri-integrations directory while updating the agent from root mode to privileged or unprivileged mode.
  • Fixed issue when running in Kubernetes where an integration configuration change provided by ConfigMap wouldn't be picked up by the agent, breaking the hot config reload feature for integrations.
Wednesday, January 29, 2020 - 15:00

Notes

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

Features

  • Added IPv6 support during hostname resolution via DNS.
  • In verbose mode, more detailed logging during hostname resolution.

Bug fixes

  • Fixed a bug from the new integrations' engine added in the version 1.8.0, which caused any JSON line larger than 64 KB to be ignored. This does not affect to the integrations that are configured with the format prior to 1.8.0, which is still supported.
  • Fixed ${config.path} replacement in new integrations' configuration file. When an integration configuration contained a config or config_file_template section and the ${config.path} variable was used in an environment variable or command-line argument, the correct path was set only during the first execution, remaining the same for the rest of executions, even if the path changes.
  • Fixed Linux packaging metadata.
    • Updated the Vendor field from "<jenkins@401c99d99b5f>" to "New Relic, Inc.", fixing the problem that some customers where having on SLES v11.2 Suse, or higher, due to the "repository vendor stickiness", which protects apps from accidentally replacing stable versions of installed packages with experimental versions from a different repository when updating.
    • Added extra metadata fields: License, Maintainer, URL, Description, Distribution and Summary
Wednesday, January 15, 2020 - 15:00

Notes

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

Features

integrations:
  - name: ssh-integration
    when:
      file_exists: /var/run/sshd.pid

The agent will execute ssh-integration only if the /var/run/sshd.pid file exists.

Bug fixes

  • Agent service wasn't stopping / restarting properly on upstart-based Linux distributions.
  • In Integration config files: Dollar symbols were unintentionally being expanded into environment variables. Before, pa$$word would have been expanded to pa${}${}word; this behavior has been corrected.
  • Improved NFS support. Read and write bytes per second were not being correctly set to 0, resulting JSON marshalling errors.
Thursday, January 2, 2020 - 17:30

Notes

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

Features

  • Inventory body reporting the agent entity ID.

Bug fixes

  • Supporting Overlay File Systems in the storage samples. Before agent 1.8.23, a device mapped from multiple overlay folders might not be reported as the parent partition but as any folder mounting it. Now the agent reports the parent mount folder.

  • Removed confusing warning log message from the integrations' engine ignoring legacy configuration files.

Pages