opentelemetry module doesn't seem to work

[metajack]

I have set my API key in the environment, but no data seems to show up at Honeycomb.io. I also tried changing the endpoint to remove the path components, since most of the Honeycomb examples don't have a path, but that didn't seem to help.

The failure test passes, which I assume means it didn't fail trying to send the message to honeycomb.

[LukeMathWalker]

Can you share your repository?

[metajack]

Sure, it is here: https://github.com/metajack/rust-telemetry-workshop/tree/metajack

[tofu511]

I had the same issue, and I could send traces to Honeycomb by downgrading the open telemetry crates. As far as I investigated, it seemed that the current crate versions in the main branch couldn't connect to Honeycomb or even didn't try to connect. I haven't found the root cause of this issue, but you can send traces by downgrading crates. https://github.com/mainmatter/rust-telemetry-workshop/compare/main...tofu511:rust-telemetry-workshop:resolve-otep-connection-issue

[tofu511]

Hi @metajack @LukeMathWalker, I found possible solutions for this issue. Either downgrading Opentelemetry's crate or changing the scheduled delay config would work.

I created a PR to change the scheduled delay config, not to downgrade the current otel's version. Would you mind reviewing it when you have a chance?

Thank you!

[imminent-despair]

Having the same issue here. @tofu511 your PR did the trick for me and now I can see the traces in Honeycomb.