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.
Solution
Required agent version: 1.0.1002 or later
The following steps mitigate the data gaps problem:
Remove the limit of one thread for the agent, allowing one thread per core.
Open the following file in your favorite plain text editor: C:\Program Files\New Relic\newrelic-infra\newrelic-infra.yml
Add the following configuration option:
max_procs:-1
Open the following file in your favorite plain text editor: /etc/newrelic-infra.yml
Use SystemD commands with CentOS 7, Debian 8, RHEL 7, and Ubuntu 15.04 or higher:
bash
$
sudo systemctl restart newrelic-infra
Use System V commands with Debian 7:
bash
$
sudo /etc/init.d/newrelic-infra restart
Use Upstart commands with Amazon Linux, CentOS 6, RHEL 6, and Ubuntu 14.10 or lower:
bash
$
sudo initctl restart newrelic-infra
bash
$
net stop newrelic-infra
$
net start newrelic-infra
Cause
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).