Your data. Anywhere you go.

New Relic for iOS or Android

Download on the App Store    Android App on Google play

New Relic Insights App for iOS

Download on the App Store

Learn more

Close icon

Max connections reached in kubernetes infrastructure agent


We have recently started seeing the following error in our new-relic-infra agent:

December 11th 2018, 09:32:26.530 time=“2018-12-11T07:32:16Z” level=error msg=“metric sender can’t process 0 times” error="InventoryIngest: events were not accepted: 503 503 Service Unavailable max connections reached: 5000

Anyone seen this before? or knows why this is happening?


Hi @idoh,

That message is due to an intermittent issue when an individual node in the cluster of nodes that comprise our collectors receives too many connections at once. Our engineering teams have been monitoring the traffic our collectors receive and are working on expanding the capacity of our cluster to help prevent this from occurring in the future.

In effect, this message indicates that the agent missed one heartbeat. This shouldn’t prove to be an issue unless you notice this error occurring multiple times in a short period.