Closed anze3db closed 1 year ago
This happens when the worker is killed and is restarted. When this happens the agent is recreated for that new worker process and the first transaction(s) is not captured while things are getting setup. After that, any following transaction will be captured.
Got it. So there is nothing we can do to fix this or disable the warning. Best to just ignore it completely?
Yes. This message is only a concern if you are not seeing data. We don't want to remove this warning as it CAN be indicative of a reason why you wouldn't be seeing data but in the case of gunicorn workers restarting like this it's expected and can be ignored. The issue with trying to not show the warning during gunicorn worker restart is that it is in a non-gunicorn specific part of the code and when the warning occurs, it occurs correctly. Meaning that the warning is indicating correctly that the process id changed and the application needs to be re-registered so while that is happening no data will be sent. To your point however, I understand how this is confusing and concerning to see this warning. This could be better explained in the docs so I'm going to add a ticket to add an explanation into the docs about this.
Description We are getting the following warning when we run
gunicorn
withnewrelic-admin run-program
:Expected Behavior The warning is not shown or a workaround is provided where the warning is not shown.
Steps to Reproduce
The warning will be shown when you open localhost:8000 in the browser.
Your Environment
Additional context
Even though this warning is emitted we are still seeing data in our new-relic dashboard, but we are still worried that perhaps not everything is being logged correctly.
Also this warning has generated 1.6k events in Sentry in our web app since yesterday.
The full debug log: