Skip to content
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

[question] spans_malformed(invalid_http_status_code) #148

Open
mcatany opened this issue Aug 21, 2024 · 4 comments
Open

[question] spans_malformed(invalid_http_status_code) #148

mcatany opened this issue Aug 21, 2024 · 4 comments
Assignees
Labels
question Further information is requested

Comments

@mcatany
Copy link

mcatany commented Aug 21, 2024

Hi,

We can see the following error in trace-agent

2024-08-20 15:36:34 UTC | TRACE | WARN | (pkg/trace/info/stats.go:101 in LogAndResetStats) | [lang:cpp lang_version:202002 tracer_version:v0.2.2 endpoint_version:v0.4 service:istio-ingressgateway.gateway] -> spans_malformed(invalid_http_status_code:13). Enable debug logging for more details.
2024-08-21 02:50:19 UTC | TRACE | WARN | (pkg/trace/info/stats.go:101 in LogAndResetStats) | [lang:cpp lang_version:202002 tracer_version:v0.2.2 endpoint_version:v0.4 service:istio-ingressgateway.gateway] -> spans_malformed(invalid_http_status_code:6). Enable debug logging for more details.
2024-08-21 09:44:59 UTC | TRACE | WARN | (pkg/trace/info/stats.go:101 in LogAndResetStats) | [lang:cpp lang_version:202002 tracer_version:v0.2.2 endpoint_version:v0.4 service:webapp-bo.alumni-connect] -> spans_malformed(invalid_http_status_code:1). Enable debug logging for more details.
2024-08-21 09:44:59 UTC | TRACE | WARN | (pkg/trace/info/stats.go:101 in LogAndResetStats) | [lang:cpp lang_version:202002 tracer_version:v0.2.2 endpoint_version:v0.4 service:istio-ingressgateway.gateway] -> spans_malformed(invalid_http_status_code:1). Enable debug logging for more details.
2024-08-21 09:48:09 UTC | TRACE | WARN | (pkg/trace/info/stats.go:101 in LogAndResetStats) | [lang:cpp lang_version:202002 tracer_version:v0.2.2 endpoint_version:v0.4 service:webapp-bo.alumni-connect] -> spans_malformed(invalid_http_status_code:1). Enable debug logging for more details.
2024-08-21 09:48:09 UTC | TRACE | WARN | (pkg/trace/info/stats.go:101 in LogAndResetStats) | [lang:cpp lang_version:202002 tracer_version:v0.2.2 endpoint_version:v0.4 service:istio-ingressgateway.gateway] -> spans_malformed(invalid_http_status_code:2). Enable debug logging for more details.
2024-08-21 11:23:19 UTC | TRACE | WARN | (pkg/trace/info/stats.go:101 in LogAndResetStats) | [lang:cpp lang_version:202002 tracer_version:v0.2.2 endpoint_version:v0.4 service:whitelabel.whitelabel] -> spans_malformed(invalid_http_status_code:1). Enable debug logging for more details.

What could it be the origin of it? We're guessing that it could come from the istio sidecar. Do you know if there have been errors related to this previously?

BR

@dmehala
Copy link
Collaborator

dmehala commented Aug 27, 2024

Hi @mcatany

It looks like the issue is coming from Istio / Envoy. This setup is a bit different from others integrations, because, while we provide the tracer, the Envoy team handles the instrumentation.

I've seen similar behavior before, where Envoy tags spans with status code outside the expected HTTP [100, 599] range. Since our Agent expects a status code within this range, those spans are flagged as malformed and aren't ingested by the trace agent.

My gut feeling is that something might be off on those requests, causing these spans to be tagged with a status code. The status code is not in a HTTP code range, maybe it's not an HTTP status code then. Are you using a gRPC or other kind of filter?

In the meantime, I strongly suggest to open a support case here for visibility.

@dmehala dmehala self-assigned this Aug 27, 2024
@dmehala dmehala added the question Further information is requested label Aug 27, 2024
@dmehala dmehala changed the title spans_malformed(invalid_http_status_code) [question] spans_malformed(invalid_http_status_code) Aug 27, 2024
@mcatany
Copy link
Author

mcatany commented Aug 27, 2024

Hi @dmehala, thanks for the response.

Yes, I opened a support ticket last week and the engineering team is supposed to be checking it. What do you mean by "filter". We use some grpc requests but I would say they aren't related to those traces...

@dmehala
Copy link
Collaborator

dmehala commented Aug 27, 2024

By filters, I was referring to Envoy filter. Unfortunately, I don't have a solution right now, but I'l give it a some thought this week, talk with colleagues and get back to you. If you can infer any pattern, that could help.

Also, just to confirm, is the support ticket for CleverTech?

@mcatany
Copy link
Author

mcatany commented Aug 27, 2024

Thanks,

The ticket is for Hivebrite number 1810265

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants