• EnglishEspañol日本語한국어Português
  • Log inStart now

Time gaps with missing data


Your New Relic infrastructure agent is up and running, but when your CPU reaches a high percentage of usage, the agent stops intermittently to submit data.


Required agent version: 1.0.1002 or later

The following steps mitigate the data gaps problem:

  1. Remove the limit of one thread for the agent, allowing one thread per core.

  2. Use your init system to restart the agent service:


The New Relic infrastructure agent, by default, runs in a single operating system thread. This may mean that, especially in Windows environments, the process scheduler gives it little chance to get CPU time when the system is overloaded.

The max_procs: -1 configuration option removes this limitation and allows the agent to use one thread per CPU core (as maximum).

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.