-
Notifications
You must be signed in to change notification settings - Fork 437
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]: otlp example does not work without configuration update #1998
Labels
documentation/examples
Improvements or additions to documentation or examples
Comments
Need a similar fix like https://github.com/open-telemetry/opentelemetry-rust/pull/1982/files to this example too. @krlohnes Would you mind sending a PR to fix? |
cijothomas
added
documentation/examples
Improvements or additions to documentation or examples
and removed
bug
Something isn't working
triage:todo
Needs to be traiged.
labels
Aug 8, 2024
Also, we need similar fix in integration tests - https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/tests/integration_test/otel-collector-config.yaml |
krlohnes
added a commit
to krlohnes/opentelemetry-rust
that referenced
this issue
Aug 8, 2024
Fixes open-telemetry#1998 With updates to the otel collector 0.104+, the collector now binds to localhost by default. The config now needs to explicitly allow access from outside the docker container.
4 tasks
lalitb
added a commit
to krlohnes/opentelemetry-rust
that referenced
this issue
Aug 14, 2024
TommyCpp
added a commit
to krlohnes/opentelemetry-rust
that referenced
this issue
Aug 14, 2024
cijothomas
added a commit
to krlohnes/opentelemetry-rust
that referenced
this issue
Oct 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I tried to run basic-otlp example and it simply didn't work.
I update the first section of otel-collector-config.yml to the following
and it started working.
API Version
0.24.0
SDK Version
0.24.1
What Exporter(s) are you seeing the problem on?
OTLP
Relevant log output
The text was updated successfully, but these errors were encountered: