use of opentelemetry Trace pipeline from agent and collector

[ajprakas]

I am using this example- https://github.com/open-telemetry/opentelemetry-collector/tree/master/examples/demo to instantiate a open telemetry agent and collector and publish spans to jaeger and zipkin backends via agent.How do I know which are the ports jaeger and zipkin receivers of agent are listening at so that I publish span to those port from my app.

after starting collector from docker-compose , I see agent, collector , jaeger and zipkin continers are running.

[anuraaga]

Hi @ajprakas - the ports for the receivers are defined in the collector config.yml files. For Zipkin, it explicitly sets 9411. For jaeger thrift http it is using the jaeger default port 14268 I believe

[ajprakas]

@anuraaga I have tried your given example with version 0.13.1 . not sure What value I should provide as channel in OtlpGrpcSpanExporter.
see my code below

it says server not found

Also I am using docker image - otel/opentelemetry-collector-dev:latest as per given example

do you have any working code as reference as given example is legacy.

[jkwatson]

We have a working example in the examples/otlp sub-project in this repository. It includes a docker-compose yaml file and a collector configuration that works.

[ajprakas]

Thanks @jkwatson given example helped me.
however service name is - OTLPRESOURCENOSERVICENAME in zipkin and nothing in jaeger as attcahed.
How do we set service name in otlpSpanExporter?

[ajprakas]

I was able to set service name via Resource and its working fine now. Thanks a ton 👍

SdkTracerProvider.builder().setResource(Resource.create(Attributes.of(AttributeKey.stringKey("service.name"), "mongo-service"))).build()

[jkwatson]

Yes, the Resource is the correct way to set the service.name going forward. Glad you found it!