-
Notifications
You must be signed in to change notification settings - Fork 522
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
Confusing log events for invalid requests #14232
Comments
hello @up2neck can you please give a bit more informations on the environment? |
Log entry was taken from APM Server logs (stdout, collected by GCP Loggins if it matters) Our team, has 2 environments (both facing the issue): My thoughts are some middleware, probably, rewrites the exact error, which leads to incorrect log entry. |
Thanks for the additional info 🙏🏼 The reason I was asking is that you may have transforms or ingest pipelines in Elasticsearch that remaps fields, in this case the
I am not aware of anything inside apm-server binary modifying the value of this field, hence my confusion as to why it is different in logs than what's stored in ES as trace. |
There are few additional steps on the top of default "APM" integration-provided ingest pipelines, we have, but all of them don't interact with |
APM Server log events and correlating trace (with self-instrumentation enabled) contains 2 different HTTP errors:
Whether log event contains 503 error with "request timed out" error:
Log entry
APM interface shown actual error was:
Trace body
The text was updated successfully, but these errors were encountered: