Problem with more then one span

I observe very strange behavior. If the application has more than one span, then information about them is not sent to the collector (I use Jaeger).

This works and I can see span in Jaeger:

  @Span('doSomething')
  async doSomething() {
    console.log('');
  }

But this code does not send any spans to Jaeger:

  @Span('doSomething')
  async doSomething() {
    console.log('doSomething');
  }

  @Span('doSomethingElse')
  async doSomethingElse() {
    console.log('doSomethingElse');
  }

I also get the same behavior if I add any nested span using TraceService or if I add any instrumentation.

I use next config:

const OpenTelemetryModuleConfig = OpenTelemetryModule.forRoot({
  metrics: {
    hostMetrics: true,
    defaultMetrics: true, 
    apiMetrics: {
      enable: true, 
      timeBuckets: [],
    },
  },
  nodeSDKConfiguration: {
    spanProcessor: new BatchSpanProcessor(new JaegerExporter({
      host: 'host.docker.internal',
      port: 6832,
    })),
    contextManager: new AsyncLocalStorageContextManager(),
    textMapPropagator: new CompositePropagator({
      propagators: [
        new B3Propagator(),
        new B3Propagator({
          injectEncoding: B3InjectEncoding.MULTI_HEADER,
        }),
      ],
    }),
    resource: new Resource({
      [ResourceAttributes.SERVICE_NAME]: 'stl',
    }),
  },
});

[pragmaticivan]

@chrismllr I’ve just added a full example: https://github.com/pragmaticivan/nestjs-otel/tree/main/examples/nestjs-prom-grafana-tempo

This one has grafana + prometheus + tempo + jaeger ui. In the logs you can copy the traceId and can search it on Jaeger UI or Tempo directly on Grafana.

[chrismllr]

@kosmos Would you mind sharing your docker-compose (or otherwise) configuration to get the messages from your nest server over to jaeger? I am having trouble with that connection, and have tried the endpoint config as well as the host/port configs.