Skip to content

otlphttp exporter #3248

Closed Answered by pellared
klempinen asked this question in Q&A
Sep 30, 2022 · 2 comments · 3 replies
Discussion options

You must be logged in to vote

By @gmreads

I got this error too, because my configured receiver didn't understand protobuff, was replying with JSON and 400.
OTLP supported backends like Jaeger work just fine

Replies: 2 comments 3 replies

Comment options

You must be logged in to vote
3 replies
@klempinen
Comment options

@dmathieu
Comment options

@gmreads
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by pellared
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
5 participants