-
Notifications
You must be signed in to change notification settings - Fork 22
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
Supply auto-configured base X-Ray tracer #3
Comments
Agree @awssandra Can you provide top common use cases where we could provide a better user experience. @anuraaga do you have the use cases you addressed in Java w auto-instrumentation? |
Can you provide top common use cases where we could provide a better user experience. Absolutely. So, the top common use case here is someone entirely unfamiliar with OTel and just wants enable it in the easiest way possible. The thing is, having to copy and paste to setup their application is unfriendly, plus they still have to require all the right packages as well. For a user who just wants to have a one-line onboarding story, the existing solution is not a great one. Here's the getting started doc today: https://aws-otel.github.io/docs/getting-started/js-sdk/trace-manual-instr#getting-the-sdk-and-dependencies We can be opinionated about our configuations, there's no need for customers to be required to do all this for a basic setup, having to do all the individual imports, the tracer config for X-Ray, the span processor etc etc. I think this can be simplified for most users just so they can try it out. Of course, we can still provide the documentation on making a custom tracer.js, but just have one top-level available that's barebones with the otlpExporter, detectors enabled, X-Ray tracer set up, would be a huge win and cut down on the reading a customer has to do. That'd also require us to vend a package with a package.json with a dependency on all the necessary OTel packages as well as both X-Ray packages, that way everything is in the same place. Ideally we could potentially reduce these steps to: Seems like we can vend several tracer files to be available out of box. They're relatively thin. |
This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled |
This issue was closed because it has been marked as stale for 30 days with no activity. |
Currently, customer have to manually create a wire up an X-Ray tracer for use with OpenTelemetry.
https://github.com/open-telemetry/opentelemetry-js/blob/master/getting-started/README.md#initialize-a-global-tracer
Unfortunately, with X-Ray's config options, this turns out to be much more in depth (yes this whole thing):
https://github.com/open-o11y/aws-opentelemetry-js/blob/master/examples/basic-xray/tracer.js
We should consider vending a ready-to-go tracer.js file for customers to use.
The text was updated successfully, but these errors were encountered: