Errors after upgrade to 7.x
See original GitHub issueDescription Data appears to be reported by both but this error is output with 7.x:
(1/ThreadPoolExecutor-0_0) newrelic.core.context ERROR - Runtime instrumentation error. Request context propagation failed. No trace with id 139977538623376. Report this issue to New Relic support.
Expected Behavior 7.x would work like 6.x
Steps to Reproduce
Run channels
with a django
project
Your Environment django 2.2.26 and channels 3.0.4
Additional context Had to add this to get the instrumentation working at all: https://discuss.newrelic.com/t/cannot-get-new-relic-to-run-with-heroku-django-gunicorn-asgi-uvicorn/93061
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Upgrading ESXi host to 7.x fails with error "invalid magic\ntar
Upgrading ESXi hosts to any version prior to ESXi 7.0 Update 3c fails; This issue can occur during all types of upgrades.
Read more >How To Troubleshooting Artifactory 7.x Upgrade Issues - JFrog
When upgrading Artifactory 6.x to 7.x versions, you may encounter some problems. The following are some of the most encountered issues and ...
Read more >DOORS Next 7.x upgrade Warning and Error codes - Jazz.net
This page is to explain the warning and error codes returned during the upgrade from DOORS Next Generation 6.x to DOORS Next 7.x....
Read more >Upgrade to ESXi 7.0: Missing dependencies VIBs Error
This error gets me from time to time, regardless which server vendor, mostly on hosts that were upgraded a couple of times.
Read more >Get help with Windows upgrade and installation errors
This could mean that the upgrade process was interrupted because you accidentally restarted your PC or signed out of your PC. Try upgrading...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Updating to
v7.4.0.172
fixed the error logs, but without the manual instrumentation mentioned in that link, no data makes it to New Relic.Here’s the versions of modules that we’re currently using:
@daveisfera you appear to be using daphne as your webserver which is an unsupported framework, which would be why you don’t see any data. You could try using uvicorn or submitting a feature request for daphne.