-
Notifications
You must be signed in to change notification settings - Fork 206
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
[BUG] Headers: invalid input for HTTPHeader #2478
Comments
I confirm, I had the same problem |
The problem was in the header, which has a value of NULL. So far I have fixed it like this
Example of a problem query in APM from tracing
|
@Sing303 Thanks for providing the additional context. I'd like to understand how null headers are entering your system. ASP.NET Core defines the headers (from which we populate those on the transaction) as |
We have not yet figured out where the null values come from, so we decided on this filter so that there would be no errors |
Okay, thanks for the response. At this point, I'm hesitant to make changes to handle nulls when, as far as I can see, they should not occur. We can review this issue if a minimal repro scenario is found. @Vaahik, do you have any further details on your scenario? |
{ |
@Vaahik, I'm trying to understand how you end up with null values for headers in the first place. |
@Vaahik Do you have any further information to help take this issue forward? |
I don`t have any diag info. Only log :( |
Can you set the APM logging level to Trace? Through setting environment variables. I got my log from these Trace logs Env variable - ELASTIC_APM_LOG_LEVEL |
I change log level to trace, but "outgoing json" do not present in the log. log: |
[2024-11-22 15:59:43.754 +04:00][57][Trace] - {HttpDiagnosticListenerCoreImpl} Request URL (http://localhost:8200/intake/v2/events) is filtered out - exiting |
@Vaahik Unfortunately, these don't help explain the root issue of how your app ends up with a null value in the header we receive. Is this a regular ASP.NET Core app? What do your @Sing303 Are you also on Centos? |
APM Agent version
The version of the
Elastic.Apm
nuget package used1.0.30 linux profiler
Environment
Operating system and version:
Centos 9
.NET Framework/Core name and version (e.g. .NET 4.6.2, NET Core 3.1.100) :
Net Core 8.0.8
Application Target Framework(s) (e.g. net462, netcoreapp3.1):
Describe the bug
APM 8.15.3
[2024-11-06 19:53:38.768 +04:00][4][Error] - {PayloadSenderV2} Failed sending event. Events intake API absolute URL: http://localhost:8200/intake/v2/events. APM Server response: status code: BadRequest, reasons: decode error: data read error: v2.transactionRoot.Transaction: v2.transaction.Context: v2.context.Request: v2.contextRequest.HTTPVersion: Headers: invalid input for HTTPHeader:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Actual behavior
The text was updated successfully, but these errors were encountered: