You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"none": No automatically configured exporter for traces.
We have split up the exporters based on protocol + serialisation to avoid taking unnecessary dependency so there is no entry point for jaeger. If someone reads the spec and follows that recommendation they will run into this error. We should either add an entry point jaeger or an alias that solves this problem.
The text was updated successfully, but these errors were encountered:
Adding an alias could result in unexpected and hard to debug behavior as someone might expect gRPC and we enable thrift or vice-versa. I think we should do the following:
Update documentation to note actual exporter names (jaeger-thrift, jaeger-grpc, etc)
Handle cases like jaeger but crash early with a helpful error messaging guiding the user towards "jaeger-thrift", "jaeger-grpc" and may be a link to docs.
From the exporters selection of spec
We have split up the exporters based on protocol + serialisation to avoid taking unnecessary dependency so there is no entry point for
jaeger
. If someone reads the spec and follows that recommendation they will run into this error. We should either add an entry pointjaeger
or an alias that solves this problem.The text was updated successfully, but these errors were encountered: