-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agent quit reporting to servers #29
Comments
Any chance you are running on Heroku? |
No. The servers were on Rackspace Cloud |
And it just happened again, well about 12 hours ago, it stopped reporting. |
Yeah, ok, it was just a dumb hunch from me. Sorry about that! |
Fixed in b13179b. Sorry for the lag, and thanks for the report! |
No problem - We just upgraded to 0.9.22 last week - haven't seen any issues yet. |
…00d924823e151ef9983db [Snyk] Upgrade newrelic from 9.4.0 to 9.5.0
Null check for context.matched
Bumps DynamoDB tap.test timeout to avoid versioned test terminations
It seems after a few days of running, the agent has quit reporting to New Relic's servers. I tooka a look at the newrelic_agent.log and it had logs in there from today, but nothing has been showing up in New Relic for over 24 hours. Restarted the workers, and I'm seeing some data flow into New Relic again
{"name":"newrelic","hostname":"*******","pid":31814,"component":"data_sender","level":50,"msg":"Got 503 as a response code from the collector.","time":"2013-05-01T22:16:23.065Z","v":0}
I've submited a ticket through our account also
The text was updated successfully, but these errors were encountered: