• /
  • Log in
  • Free account

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).

For more help

If you need more help, check out these support and learning resources:

Create issueEdit page
Copyright © 2021 New Relic Inc.