Open AA-morganh opened 7 months ago
I think we're facing the same issue right now, something changed and broke collector in some minor version update for node
EDIT: This is due to us moving forward and migrating whole project to ESM, downgrade to 18.16 and using experimental flag fixed it
# https://gajus.com/blog/how-to-add-sentry-tracing-to-your-node-js-app#nodejs-esm-modules
# https://github.com/open-telemetry/opentelemetry-js/issues/4392
# https://github.com/open-telemetry/opentelemetry-js/issues/4547
# https://github.com/open-telemetry/opentelemetry-js/issues/4553
CMD ["node", "--experimental-loader=@opentelemetry/instrumentation/hook.mjs", "dist/index.js"]
Though I talked with my team and we wont do it for production build, so I think we gotta live with no x-ray for a time
Hi, I'm having an issue with ADOT on ECS Fargate. I'm seeing cloudwatch logs, metrics, and container insights metrics, as well as some start-up FS spans in X-RAY, but I'm not getting any application spans in X-Ray. My auto instrumentation code is as folows:
My TaskDef looks like this (my CI replaces a bunch of tokens in here):
I have verbose logging enabled on both the sdk and on the collector, and I'm not seeing anything that looks suspicious to me, other than that I don't see my expected automatic or manual spans.
On a local docker-compose setup with a simple mainline otel collector I do see my spans making it to a grafana/tempo instance, so I think the instrumentation is largely set up correctly. Any guidance would be a huge help.