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

Board Review: Distributed Tracing Preview 2 #524

Closed
SuyogSoti opened this issue Jul 24, 2019 · 2 comments
Closed

Board Review: Distributed Tracing Preview 2 #524

SuyogSoti opened this issue Jul 24, 2019 · 2 comments
Assignees

Comments

@SuyogSoti
Copy link

https://gist.github.com/SuyogSoti/3b1d8b22f40eb3c1f34300a0565db55e

This gist tries to clear some up confusion up. There are 2 main confusions to clear up.

  1. When is the tracing enabled for each languages
  2. What spans should be generated when the user writes certain code.
    1. Regular requests vs Paging vs Polling?
    2. How does Authentication and caching show up?

Related to: #501 #507

@SuyogSoti SuyogSoti added architecture board-review Request for an Architectural Board Review labels Jul 24, 2019
@adrianhall adrianhall removed the board-review Request for an Architectural Board Review label Jul 25, 2019
@adrianhall
Copy link
Member

We just did a distributed tracing meeting with the arch board where this was covered. Can you please work with @johanste to get specific answers to your questions?

@adrianhall adrianhall removed their assignment Aug 6, 2019
@johanste
Copy link
Member

I believe all these issues were covered in the meeting. Tracing requires opt in. Paging and polling, each outgoing request is traced. No relationship between requests (links) for preview 2. Authentication, each individual request is traced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants