-
Notifications
You must be signed in to change notification settings - Fork 3
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
Ensure "received invalid w3c traceparent" has resolved #665
Comments
Update: I updated the exclusion rule from 99% to 99.99%, because it was still allowing too many logs. |
Update: I moved the retention rule up so it happens before the EKS rules. Additionally, we may ultimately need a DD support ticket for this, if the DD trace support ticket doesn't resolve this. |
Currently, I do not see any instances of this log message in the last one month, however, the exclusion rule is currently set to 100%, so there would be no records kept. I have not seen it appearing in Live Tail after 15 minutes. I think we can update the retention rule to something like 0% and then check back in 24 hours. If no logs, we can remove the retention rule and call this ticket complete. |
I have updated the retention rule to exclude 0%. Now we wait... |
We have logged almost 36k of these since the exclusion was turned off yesterday So, it appears this is not yet fully resolved. Over 95% of the messages are in the edx-analytics-api repo, and a handful % is from LMS. I will move the exclusion rule back to 99% so that it is still apparent, but not costing us much $. |
Our hypothesis is that logs with "received invalid w3c traceparent" will resolve once New Relic is no longer enabled. We think New Relic may be setting a trace header that gets misinterpreted by Datadog.
We need to do the following in order:
The text was updated successfully, but these errors were encountered: