-
Notifications
You must be signed in to change notification settings - Fork 791
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
Add exporter factory for JaegerThriftSpanExporter #1868
Add exporter factory for JaegerThriftSpanExporter #1868
Conversation
I suspect you'll need okhttp & jackson to be shaded in there, but I'm not sure. |
What's the best way to find that out? |
hey @breedx-splk! jaeger and otlp just need some grpc-netty artifact, seems we picked grpc-netty-shaded, but that's not related to the agent shading. the exporters live in the AgentClassLoader, where things aren't shaded, except for references to otel API, SLF4J and j.u.l. which need to talk to our shaded versions of those libraries that are in the bootstrap class loader. does the collector have a jaeger-thrift pipeline, so we can add a smoke test similar to JaegerExporterSmokeTest? also, can you submit a separate PR updating the README.md with the new exporter details? we'll merge the doc PR separately when the next release goes live |
smoke-tests/src/test/groovy/io/opentelemetry/smoketest/JaegerThriftExporterSmokeTest.groovy
Show resolved
Hide resolved
* add exporter factory for JaegerThriftSpanExporter * add smoke test
This resolves #1609
I just followed the existing patterns/conventions.
I wasn't entirely sure why the jaeger grpc exporter needed the shaded netty, so I didn't bring it over. Does this exporter need something similarly shaded?