Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Runtime instrumentation error. Request context propagation failed. No trace with id {ID}. Report this issue to New Relic support.
See original GitHub issueHi there, After upgrading from version 7.2.2.169 to 7.2.4.171, we started to receive a lot of events (459k) in our Sentry with the next message:
Runtime instrumentation error. Request context propagation failed. No trace with id 139701399167680. Report this issue to New Relic support.
We are using the next tech stack:
- Python v.3.8.12
- Django v3.2.9
- Django Channels v3.0.4
- New Relic v7.2.4.171
Command which we run to start our gunicorn:
newrelic-admin run-program gunicorn asgi -k uvicorn.workers.UvicornWorker
Seems like it was introduced after that PR
As a temporary solution, we downgrade our version to 7.2.2.169.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Same error here
I’m running with daphne as follows
newrelic-admin run-program daphne -b 0.0.0.0 -p 8000 application.asgi:application --access-log - --verbosity 3
channels==3.0.4 daphne==3.0.2 django==3.2.9 newrelic==7.2.4.171
Hi @umaannamalai , Created new topic in forum.