Infrastructure agent release notesRSS

Notes

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

Features

• Fixed issue that caused long running integrations to continue running after the agent was stopped.

Notes

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

Features

• Added new config options: file_devices_ignored, allowed_list_process_sample

Notes

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

Features

• Log warning when OHI amount of entity attributes exceeds 240.
• Removed warning message when system can't find upstart integration.

Notes

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

Features

• Containers' discovery allows you executing your integrations within a set of containers that are dynamically discovered at runtime. It also allows dynamically configuring your integrations to match the container's data (labels, ports, IPs...). Currently, Docker and Fargate containers are supported. For more information, please check the container auto-discovery documentation.
• Secret variables binding allows you passing secrets (users, passwords...) to your integrations without having to write them as plain text in your configuration files. Currently, Vault and Amazon KMS are supported. For more information, please check the secrets management documentation.

Notes

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

Bug fixes

Fixed graceful stop that was previously behaving non-optimally under system load circumstances:

• Introduced within the new newrelic-infra-service binary at v1.5.59.
• This affected cpu_profile option, restored now.

Notes

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

Bug fixes

• Reverted previous changes of version 1.5.62 because there are some edge cases not handled properly. We'll bring back the feature as soon as possible.

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.