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 tocom.newrelic.redis
andintegrationVersion
to1.4.0
- For example, when using the Redis monitoring integration
nri-flex
has been upgraded to versionv1.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 becomenewrelic-infra-<version>-1.el8.x86_64.rpm
when published.
- The RHEL8 package
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 thanintegration/<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 underinventory/com.newrelic.redis
- For example, when using the Redis monitoring integration before it would create inventory under
- 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.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Added
All the distributions of the Agent (packages, containers...) are shipped with
nri-flex
andnri-docker
integrations, so you don't need to install them anymore.- Agent Linux package and containerized agent both now include nri-docker. Before, only the package did.
- Agent Linux package and containerized agent both now include nri-flex. Before, none did.
New containerized agent "bundle" was created from https://github.com/newrelic/infrastructure-bundle , and published at (DockerHub)[https://github.com/newrelic/infrastructure-bundle]. "Bundle" container can now be released and included agent and integration versions could be tracked from the GH repository tags and
versions
file.
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).
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.