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

HTTP PRI method in Traces #798

Open
MA3CIN opened this issue Apr 26, 2024 · 2 comments
Open

HTTP PRI method in Traces #798

MA3CIN opened this issue Apr 26, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@MA3CIN
Copy link
Contributor

MA3CIN commented Apr 26, 2024

Describe the bug

This might be a Free5GC issue more than otel, but i am still hoping you can guide me in the right direction.
I'm using the Opentelemetry Operator with the Instrumentation CRD to instrument (get traces from) Free5GC. When analysing the traces obtained via Otel, i see unusual traces (with long spans of >1second) with the HTTP PRI method:

image

These PRI traces are certainly unexpected to say the least. The HTTP PRI method "is never used by an actual client. This method will appear to be used when an HTTP/1.1 server or intermediary attempts to parse an HTTP/2 connection preface." (based on https://webconcepts.info/concepts/http-method/PRI). So i imagine this means that the HTTP requests are send between a client and a server where there is an HTTP version mismatch?

Otherwise the logs on both otel instrumentation container and the otel operator seem clean:

image

image

Environment

  • OS: Ubuntu 20.04 LTS Kernel v 5.15.0-105-generic
  • Go Version: 1.17.8 (Free5gc)
  • Version: otel operator latest, same with instrumentation

To Reproduce

Steps to reproduce the behavior:

  1. Deploy Otel Operator, Go Instrumentation, Free5GC (latest) and Jaeger.
  2. View logs from the otel sidecar container or traces in Jaeger
  3. Observe unusual traces with HTTP PRI method.
@MA3CIN MA3CIN added the bug Something isn't working label Apr 26, 2024
@MA3CIN
Copy link
Contributor Author

MA3CIN commented May 5, 2024

I'd love to get some input from you, to at least guide me in the right direction (is this a Free5GC related problem?)

@RonFed
Copy link
Contributor

RonFed commented May 7, 2024

@MA3CIN I'm not familiar with Free5GC. Is it expected to be an HTTP2 server? Is the client using HTTP2?
Currently, our tests do not cover instrumenting HTTP2.
You can use a packet sniffing tool to see what is being sent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants