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 whencgroup
was not mounted in the standard path/sys/fs/cgroup
. Now it can discover differentcgroup
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.
- This version fixes missing Docker container metrics improving Linux
- Fixed permissions to
/tmp/nri-integrations
directory while updating the agent from root mode to privileged or unprivileged mode.- This changes the owner of the
/tmp/nri-integrations
folder, which is used by some integrations and the Infrastructure integrations SDK to cache data.
- This changes the owner of the
- 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.
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 aconfig
orconfig_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
andSummary
- Updated the
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Features
- Now the Infrastructure agent, when running on Linux, can collect Docker container metrics like CPU, memory, I/O and network. This feature is enabled by default for all supported Linux OSs. Please, ensure the host meets the requirements.
- The new integration config files now support the
when
section. It allows you to control the execution of an integration if a given file exists. Here's an example:
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 topa${}${}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.
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.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Features
- Removed recurring warning message flooding the logs which was introduced in release v.1.8.4
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Features
- Added "Host Not Reporting" alert condition support, in order to avoid getting alerted on expected cluster downscaling.
Further details: https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/i...
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Features
- Added "Smart Verbose" mode. Once enabled most recent debug messages will be shown whenever an error is logged.
- The maximum number of cached entries are configured through the "smart_verbose_mode_entry_limit" attribute (defaults to 1000).
- To enable "Smart Verbose" mode, set the verbose config value to 2.
- Auto-discovery enhancements: (will update this soon)
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Features
- Implemented disconnect call when the agent detects that the host is shutting down.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Features
- Fixed command channel URL for EU
- Preventing certain combinations of new integrations configuration (introduced in 1.8.0) crashing the agent
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Features
New integrations engine, which coexists with the previous engine for backwards-compatibility and smoother transition. Featuring:
- Simpler setup of integrations, with fewer files and fewer mandatory properties. In some cases, you only have to set the integration name to enable it.
- Flexible configuration of integrations via command-line arguments, environment variables, or external files.
- Ability to group different integrations in the same configuration file.
- Hot reload of integrations, so you can add a new integration or change its configuration without needing to restart the Infrastructure agent.
- Timeouts when an integration does not respond before a user-specified time. The integration process is killed and restarted. This can also be disabled.
- Smooth migration from the old integrations engine.
Please read the documentation about Infrastructure integration configuration file specifications for agent v1.8.0 or higher for a complete description of how to start using the new integrations engine, as well as a detailed description and examples of the new configuration options.