-
Notifications
You must be signed in to change notification settings - Fork 195
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] otel-trace-source is not accepting traces in OTLP format via HTTP #1152
Comments
Hi @tmarszal, Thanks for creating this issue! I have recreated the 404 failure and am looking further into it. |
After doing some investigation, it was found that the Armeria servers support
exporters:
otlphttp/2:
traces_endpoint: http://data-prepper:21890/opentelemetry.proto.collector.trace.v1.TraceService/Export
insecure: false
insecure_skip_verify: true
headers:
"Content-type": "application/protobuf"
otel_trace_source:
ssl: false
unframed_requests: true Again, thanks for finding this. We should definitely have an example usage of |
Hi @graytaylor0 , Thank you for a quick reply. Your changes worked for me on the example. However, they did not when I tried migrating the changes to my environment. I keep getting HTTP 500 as a response to the request from opentelemetry-collector to data prepper, but there is no indicator of any problems in data prepper logs. What I noticed is that the example uses opentelemetry-collector:0.24.0, while the latest one is 0.46.0 (I am using 0.45.0 at the moment). I am also getting the same error in example after bumping collector to 0.45.0 in
Tomorrow I am going to enable more detailed logs and/or debug data prepper to see what's the underlying issue there. |
I inspected HTTP 500 response to opentelemetry-collector and found out there was
So the last question from me is if it is possible to enable compression on data-prepper side? I was not able to find anything regarding that in the documentation. |
Glad you were able to get it working. Right now, there is no way to enable compression on the data-prepper side. Would you like to have an issue created for this feature? |
@graytaylor0 Thanks for confirming! I will create it myself as an enhancement suggestion 👍 |
Describe the bug
OTel Trace Source claims to support OTLP Protocol using both OTLP/grpc and OTLP/HTTP. I am not able to make the latter work. (It's a limitation of my runtime environment that I can only use HTTP for now.)
To Reproduce
jaeger-hotrod
example from the repositoryotel-collector-config.yml
:otlp
tootlphttp
on lines 7 and 16data-prepper:21890
tohttp://data-prepper:21890
on line 8docker-compose up -d --build
docker logs otel-collector
docker-compose rm -s -v
Expected behavior
I expected the messages to come through, just as they do when using unmodified
otel-collector-config.yml
.Environment (please complete the following information):
Additional context
I can't see any implementation for OTLP/HTTP in https:/opensearch-project/data-prepper/tree/main/data-prepper-plugins/otel-trace-source/src/main/java/com/amazon/dataprepper/plugins/source/oteltrace
The text was updated successfully, but these errors were encountered: