Replies: 1 comment
-
After some testing, this looks to be related to using |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to use manual instrumentation of the NodeTracerProvider, and during shutdown, trying to force an await on
provider.shutdown()
. However this doesn't seem to be working as expected. If I instead add a 5 second delay to my application before it exists, the traces send without issue. I'm using a local otel-collector validate this usingdocker run --rm -p 4317:4317 -p 4318:4318 -v ./config.yaml:/etc/otel-collector/config.yaml -e OTEL_LOG_LEVEL=DEBUG otel/opentelemetry-collector-contrib:latest
I tried to provide a simple example using the code below, run with
npx ts-node --require ./telemetry.ts ./index.ts
Any insight as to why the
await
is not properly waiting for the provider to shutdown and flush?telemetry.ts
index.ts
Here's my collector
config.yaml
I'm using to view when the spans successfully make it to the collectorconfig.yaml
Beta Was this translation helpful? Give feedback.
All reactions