1.14.0

Notes

A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent.
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months.

Changed

• Integration protocol v4:
  • Log entity registration errors / warning only when debug is enabled.
  • Fix logic that checks max entity batch in bytes.
• #224 Allow list of infrastructure event fields restructured as deny list so that additional fields can be included.
• #235 Updaed HTTP API to support all kind of integration payload versions, added support for exposing integrations API via raw TCP socket.
• #268 Update curl version to fix CVEs
• Bundled integrations:
  • Flex integration has been updated to version 1.3.7. For more information, see the nri-flex changelog.
  • Docker integration has been updated to version 1.4.1. For more information, see the nri-docker changelog.
• Log forwarder:
  • #255 Parser renamed to filter.
  • #255 Removed deprecated folder parameter.

Added

• Secrets & env-vars support:
  • #251 Agent configuration secrets (databind variables block) support.
  • #260 #263 #266 Added environment-varibles expansion support for agent & integration configuration files.
  • #258 Added New Relic CLI obfuscated support for secrets.

1.13.2

Notes

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

Added

• #126 The embedded telemetry API, responsable for sending dimensional metrics, now limits the amount of queued entities. This feature tends to avoid memory consumption when metrics can not be submitted.
• Agent and on-host integrations are now supported on Ubuntu 20.04 LTS (focal).

Changed

• #222 The built-in Docker integration has been updated to version 1.3.3. For more information, see the nri-docker changelog.
• Log forwarder feature has updated Fluent Bit plugging to version v1.6.3 and Fluent Bit Output for New Relic to v1.4.3. For more information about Logging feature, see our docs.

1.13.1

Notes

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

Added

• #155 The Infrastructure agent now handles entities' registration errors the following way (Infrastructure SDK v4 protocol):
  • For request errors:
    • Connectivity failure or limit exceeded (429 or 503 status codes) will trigger a retry with an exponential backoff with a maximum backoff of 1 minute.
    • Other types of errors (including bad payload format) will be logged, and data will be discarded.
  • For successful requests (200 status code) containing:
    • Errors: The agent will discard related data.
    • Warnings will be logged.
• #156 The Infrastructure agent entity registration now batches requests with a maximum of 1000 entities and payloads of 1Mb per call.
• #123 The embedded telemetry API now splits DM submission by number of entities following requested driven contract limitations.
  For more informations on the limits, see our docs

Changed

• #206 The built-in Prometheus integration has been updated to version 2.3.0. For more information about the Prometheus integration, see our documentation.

Fixed

• #203 NFS invalid stats fix.
• #188 Prometheus summary type calculated as delta value to properly allow average calculation in NRQL.
• #167 Container processes now correctly filtered as host processes when Process Monitoring is enabled and "include_matching_metrics" rules are defined. For more information about enabling process monitoring and filtering processes, see our documentation.

1.13.0

Notes

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

Added

• #172 The Infrastructure agent now includes the nri-prometheus v2.2.1 integration embedded with Linux packages and Docker image.
  For more information about the Prometheus integration, see our docs

• #152 Integrations with protocol v4 are now being registered and stored in memory by their unique entity name.

• #125 Improvements in protocol v4 dimensional metric submission.

Fixed

• #177 The Infrastructure agent now properly handles nested inventory items.

1.12.7

Notes

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

Added

• (#141) Support for prometheus summary and histogram metric types in the infrastructure SDK protocol v4.
• (#145) Integrations based on SDK protocol V4 now submit events with the registered entity ID.
• (#146) Log improvement to increase visibility when troubleshooting service failures.
• (#164) Log forwarder feature supports verbose mode of Fluent Bit when running the agent in verbose mode. This will greatly help when troubleshooting Log Forwarder issues.
  For more information about Logging feature, see our docs

Fixed

• (#149) Host might start reporting as different entity when running on the cloud and the cloud API couldn't be reached or returned an error.

1.12.6

Notes

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

Added

#131 Dimensional metrics will be sent using collector_url configuration for fedRAMP compliance.

Fixed:

#137 A bug in how collector_url is calculated to be FedRAMP compliance.

For more information FedRAMP compliance, see our docs

1.12.5

Notes

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

Added

#53 Dimensional metrics are now processed by the agent, registering entities for them. This feature is disabled under a feature-flag.
#90 The log forwarder now captures the name of the file being tailed as Path_Key.
#96 The agent now supports accessing secrets from CyberArk either using an HTTP endpoint or the CLI tool.

For more information on secrets management using CyberArk, see our docs.

Fixed

#101 Fixed issue where the agent would panic when trying to compact inventory data.

Changed

#109 The built-in Flex integration has been updated to version 1.3.5. For more information, see the Flex changelog.
#108 curl has been updated to 7.69.1-r1 in the base image.

1.12.4

Notes

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

Added

#77, #84 The Log Forwarder now supports Winlog events and allows EventID filtering

For more information on the Log Forwarder, see Forward your logs using New Relic Infrastructure (Winlog).

Fixed

#75 Fixed a bug that produced this error message can't save submission time when incorrectly trying to save submission time for the host entity that was not required.

Changed

#82 The built-in Flex integration has been updated to version 1.3.4. For more information, see the Flex changelog.
#78 Upgraded fsnotify to v1.4.9 to improve the detection of file system changes.

1.12.3

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

• 14bcf94 The built-in Docker integration has been updated to version 1.3.2. For more information, see the nri-docker changelog

1.12.2

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.