-
Notifications
You must be signed in to change notification settings - Fork 64
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
RabbitMQ: NR agent version 8.39.2 overwrites message headers #639
Comments
I think I have some lead. Take a look at the RabbitMQ API: However in:
Correct me if I am wrong, but it will always result in Now, in my case, the |
What's surprising is: why does it work in 8.37.0… So, when I have upgraded NR to 8.39.2 – the only headers our application messages had: It looks like NR 8.37.0 does not intercept the: |
I have the same issue. Thanks for reporting! I hope it will be fixed soon! 🤞 |
Thank you for the bug report and investigation @witoldsz! As you identified, we did recently add instrumentation to some RabbitMQ calls. The team discussed this issue in the standup today and we are looking at a fix. |
Thanks for writing this up @witoldsz. I agree with your analysis of what the issue is. Hopefully we can get a fix out soon. |
@witoldsz @lstachowiak We just merged a PR that should fix this issue, which auto-closed this issue. The fix will be available in the next release. I am not sure when we plan to do the next release, it might be as early as next week. Thanks again for the report and the analysis. |
thank you for such a quick response!!! |
@nr-ahemsath thank you. I saw the PR and as far as I can tell, it will crash our application: #648 (comment) |
Description
After upgrading NewRelic agent 8.37.0 to 8.39.2 our services started to fail due to missing headers in RabbitMQ messages.
Expected Behavior
New Relic should not overwrite application's headers with it's own.
Steps to Reproduce
Application written in F# 5, publishing messages looks like this (simplified)
Your Environment
Additional context
Nothing yet, work in progress…
The text was updated successfully, but these errors were encountered: