Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Bug fixes
- When a wrong agent id was set up prior to have a cloud-id, agent was not able to migrate to a new more stable id once it got cloud-id. Now agent id is updated and new data is therefor attached to this more stable cloud-id.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Changed
- Agent service binary is now
newrelic-infra-service
instead ofnewrelic-infra
. Later is now a child process spawned by the prior. See further details.
Added
- Command channel. Enables NR platform to trigger commands to agents via command-api HTTPS endpoint . See further details.
- Added log entry for when initializing docker client fails:
unable to initialize docker client
.
Bug fixes
- Disabled keep-alive on cloud metadata requests to avoid leaking open connections.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Changed
Linux
- Better error handling for NFS support.
- HostInfo plugin to provide uptime for older distros.
Bug fixes
- The agent will reuse network connections again. Since v1.3.18, the agent created a new connection on each metrics post. Not reusing the connections may lead metrics to be accumulated and submitted with long delays in systems where the connection establishment is slow.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Added
- Linux: Added additional checks to confirm the user ID to determine whether the agent is running as a root user.
Changed
- Using a new endpoint for Agent identity retrieval to mitigate the hostname flipping issue. This change was introduced for the Windows Agent 1.5.37, and now is also active for the Linux Agent.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Added
Added new NFSSample (event type is NFSSample) for gathering NFS client metrics. This is configurable by the following config option:
metrics_nfs_sample_rate
(default: 20)detailed_nfs
(default: false)
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Changed
Add extra information on verbose logs. On each metrics post, an incremental counter and the timestamps of the submitted metrics are logged.
Windows specific
Using a new endpoint for Agent identity retrieval to mitigate the hostname flipping issue.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Changed
- Improve trial management mechanism in Agent
- Add support for including extra attributes in the Events; before, events only supported a summary and category field, now extra attributes can be defined.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Changed
- Optimized Storage Sampler CPU consumption (noticeable in agents managing > 100 mounted devices).
Windows specific
- All executables are now signed.
- Added versioning info to newrelic-infra-ctl.exe.
- These changes should avoid Defender to flag the package as threat.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Windows only
- Previous agent version 1.5.0 got flagged by Windows Defender. We found it was a false positive. This version proved to pass Defender test, but could still get flagged by Defender on some systems.
- Improved
StorageSample
metrics performance. Please refer to the New Relic event data dictionary for a detailed description of them.
Notes
A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent.
Changed
- Improved
StorageSample
metrics performance.- Please refer to the New Relic event data dictionary for a detailed description of them.
Windows only
IMPORTANT: This version was deleted from the Windows repository to avoid causing issues on the platform.
- Improved hostname flipping issue mitigation using a new endpoint for agent identity retrieval.
- Cases where a host flipping its hostname (because DNS lookup is not available or any other reasons) caused host entity identification to change (and some alerts to fail) should be mitigated, but some cases could still persist.