Skip to content

Releases: newrelic/infrastructure-agent

1.12.3

19 Aug 15:36
e0e2ab7
Compare
Choose a tag to compare

Notes

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

Added

  • a7b17c6 Inventory data collection now is works in a non-blocking manner: We now allocate a configurable inventory queue in the same fashion as metrics/events.

Fixed

  • 71cc96b Fixed issue in the storage sampler where we reported only one mount point for each device.

Changed

1.12.2

07 Aug 08:45
25b36d4
Compare
Choose a tag to compare

Notes

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

Fixed

  • PR-59 This fixes inventory errors showing up on the log for "DEBUG" level with message "error field deltas not in expected order: have delta ID XXX, want YYY".
Context

Inventory deltas are JSON diffs and they need to be applied in order aiming to provide a consistent state. Both New Relic agent & platform stored their latest delta ID received/submitted.

This delta ID is incremented in each plugin entity inventory submission to platform.

When these IDs go out of sync between agent and platform, the later provides its latest known ID for the given inventory plugin & entity. Then a reconciliation process is run by the agent for that plugin so next ID will match expected platform one.

Root cause

For remote (non host) entities the agent side didn't store delta IDs in a per entity basis as platform did. This means for a given inventory plugin or integration providing more than 1 entity there'll be delta ID order issues, which are only seen on agent's DEBUG level (verbose mode > 0).

At some point all data will usually be submitted as reconciliation process attempts to fix this. But for high load integrations producing multiple remote entities this reconciliation process will be triggered every time an entity needs to be submitted as for each of them platform keeps a record, while agent recorded ID in a per plugin basis. Therefore for high-load integrations agent reconciliation process might enter in race-condition loop trying to fix these delta IDs.

Fix

This release fixes this behaviour by keeping track of delta IDs in the same way platform does (in a per plugin & entity basis).

As state might be stored in disk for inventory deltas, in case any integration had it persisted before the fix it'll take a reconciliation run per entity to fix agent locally stored IDs. In this case you might still see some log entries, but they'll be gone during their first submissions.

1.12.1

23 Jul 12:21
Compare
Choose a tag to compare

Notes

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

Added

Fixed

  • d35cbe7 Fixed the sending of heartbeat samples to New Relic.
  • 6503df0 Inventory is now fully re-sent if the host has been offline for 24 hours or if the agent ID changes.
  • 4ccd9ff Fixed issue where running Docker auto discovery was leaking file descriptors.

1.12.0

15 Jul 17:27
5a97e82
Compare
Choose a tag to compare

Notes

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

Processes metrics can be enabled for new accounts

By default, the Infrastructure agent doesn't send data about the operating system's processes. The agent still collects such data, unless metrics_process_sample_rate is set to -1.

The sending of processes data to New Relic can be manually enabled by setting enable_process_metrics to true. To fine-tune which processes you want to monitor, configure include_matching_metrics.

Accounts and subaccounts created before July 20, 2020 have enable_process_metrics set to true by default; this can be
overridden by setting a different value in the config file.

Added

  • f670501 Added ReadWriteBytesPerSecond to storage sampler.

Fixed

  • 1c06e93 Improved the handling of child process on Windows.
  • 3394abd Fixed a bug where Logs in Context wouldn't map to an application when using the Infrastructure forwarder
  • Updated KMS Secrets management to work correctly with credential_file and config_file.
  • Removed some potential race conditions in the agent which should improve the stability of the agent.
  • Fixed issue where storage sample would sometimes not report storage devices correctly

Changed