-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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]: Jaeger v1.59 doesn't accept OpenTelemetry data on ports 4317/4318 #5737
Comments
Yes I have the same problem that we have already discussed here. With older image version like the 1.58 of the jaeger-all-in-one it works fine. |
Most likely due to recent OTEL Collector change to default receivers to use The workaround is to pass host IP explicitly to Jaeger, e.g. via these env variables, as in this fix:
Alternatively, refer to OTEL guidelines https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks |
@yurishkuro Yep, it works when I added those two lines :) |
## Which problem is this PR solving? - Resolves #5737 ## Description of the changes - Revert #5734 - Default OTLP receiver endpoints to `:port` instead of relying on OTEL Collector defaults - Clean up tests to use ephemeral ports when possible ## How was this change tested? - Tested similar to #5734 by using `COLLECTOR_OTLP_HTTP_HOST_PORT=:4318` --------- Signed-off-by: Yuri Shkuro <[email protected]>
jaegertracing/jaeger#5737 Signed-off-by: Andrew Haines <[email protected]>
* chore(deps-dev): update development dependencies Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * Update transitive dependencies Signed-off-by: Andrew Haines <[email protected]> * Configure Jaeger's OTLP collector to listen on all addresses jaegertracing/jaeger#5737 Signed-off-by: Andrew Haines <[email protected]> --------- Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Signed-off-by: Andrew Haines <[email protected]> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Andrew Haines <[email protected]>
In the next release we are going back to listening on all IPs. |
Due to a recent change in the OpenTelemetry Collector, Jaeger didn't accept OpenTelemetry data anymore. Until this change is reverted upstream, we explicitly pass the the host IP to Jaeger as a workaround. See jaegertracing/jaeger#5737 for more information.
Due to a recent change in the OpenTelemetry Collector, Jaeger didn't accept OpenTelemetry data anymore. Until this change is reverted upstream, we explicitly pass the the host IP to Jaeger as a workaround. See jaegertracing/jaeger#5737 for more information.
Due to a recent change in the OpenTelemetry Collector, Jaeger didn't accept OpenTelemetry data anymore. Until this change is reverted upstream, we explicitly pass the the host IP to Jaeger as a workaround. See jaegertracing/jaeger#5737 for more information.
See this ticket for more info - open-telemetry/opentelemetry-collector-contrib#33995
What happened?
When I try to export metrics to jaeger via OTLP collector it fails with the following error. What is causing this given the fact that it was working a few weeks back?
The text was updated successfully, but these errors were encountered: