Replies: 1 comment
-
The ZipkinExporter bad request error was fixed by adding a zipkin receiver and by specifying it on the traces receivers' pipeline. The OtlpExporter, however, doesn't work. Tried with both HTTP & GRPC, with and without the path of |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone.
I've got a little problem while using OpenTelemetry on my app C# app (with EF Core and WebAPI).
Environment:
I've configured the app to export the data to Otlp collector (running on docker) like this:
Collector config:
I've left the docker compose file attached to the message, in case somebody needs to look at it.
Anyways, using wireshark, on the wsl2 vm, I can't capture any traffic with a POST to /v1/traces
However, if I change from OtlpExporter to ZipkinExporter and leave the OTLP Collector address and path there, I can see a /v1/traces request but I get a 400 BAD Request response (from C# app to the Collector Container). If the address of ZipKin exporter on the C# app is
http://localhost:9411/api/v2/spans
, it works fine.From what I've understood so far, based on my testings:
Cases:
http://localhost:4318/v1/traces
doesn't show logs on the otel-collector and there's no traffic on wiresharkhttp://localhost:9411/api/v2/spans
works like a charm (since the app on windows sends directly to zipkin)http://localhost:4318/v1/traces
, with content type json and a well-formatted body, allows collector to receive the data.Attempts with other envs:
Docker compose file:
Beta Was this translation helpful? Give feedback.
All reactions