Skip to content
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

[tracking issue] Ability to trace web apps #723

Closed
4 tasks
yurishkuro opened this issue Mar 2, 2018 · 1 comment
Closed
4 tasks

[tracking issue] Ability to trace web apps #723

yurishkuro opened this issue Mar 2, 2018 · 1 comment
Labels
help wanted Features that maintainers are willing to accept but do not have cycles to implement meta-issue An tracking issue that requires work in other repos

Comments

@yurishkuro
Copy link
Member

yurishkuro commented Mar 2, 2018

Currently Jaeger does not directly support starting traces from the web browsers, although it is theoretically possible by using zipkin-js client (however it would force the rest of the services into zipkin's B3 headers).

The following is required:

The user application that would serve the Web app would either need to set up CORS headers to allow Jaeger client to submit traces to a different address, or to proxy those submissions to Jaeger collector.

@pavolloffay
Copy link
Member

Closing this as we are not planning to work on client libraries anymore. This functionality should be available in OpenTelemetry collector.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Features that maintainers are willing to accept but do not have cycles to implement meta-issue An tracking issue that requires work in other repos
Projects
None yet
Development

No branches or pull requests

3 participants