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

Zipkin follow ups #960

Closed
3 tasks
mattklein123 opened this issue May 14, 2017 · 13 comments
Closed
3 tasks

Zipkin follow ups #960

mattklein123 opened this issue May 14, 2017 · 13 comments
Labels
area/tracing enhancement Feature requests. Not bugs or questions. help wanted Needs help!

Comments

@mattklein123
Copy link
Member

Might be a few other things missing. Feel free to add.

cc @adriancole @timperrett @rshriram @fabolive

@mattklein123 mattklein123 added enhancement Feature requests. Not bugs or questions. area/tracing labels May 14, 2017
@fabolive
Copy link
Contributor

@mattklein123 Your list sounds like a great starting point for improvements. I should be able to start tackling that next week.

@mattklein123 mattklein123 modified the milestone: 1.4.0 May 19, 2017
@kyessenov
Copy link
Contributor

Is there some plan to filter or sample traces for zipkin?

@mattklein123
Copy link
Member Author

Is there some plan to filter or sample traces for zipkin?

@kyessenov what do you mean exactly? Sampling is already supported (only via runtime, can be trivially added to the config). What do you mean by filtering?

@rshriram
Copy link
Member

rshriram commented Jun 8, 2017

btw, part 3 of this is done.. #993

@codefromthecrypt
Copy link
Contributor

codefromthecrypt commented Jun 9, 2017 via email

@codefromthecrypt
Copy link
Contributor

codefromthecrypt commented Jun 9, 2017 via email

@mattklein123 mattklein123 modified the milestones: 1.4.0, 1.5.0 Jul 21, 2017
@mclarke47
Copy link

mclarke47 commented Jul 25, 2017

@mattklein123 I think filtering refers to excluding endpoints that you probably don't want to trace such as admin resources or health check endpoints. Would be helpful for this istio issue.

@mclarke47
Copy link

I think that another follow up action should be to support 128 bit trace ids (details reasons).

@codefromthecrypt
Copy link
Contributor

Hi, @flier I know this isn't your code, but since you are helping with zipkin in c/c++.. There are a lot of users who'd like this issue to be improved, but less people actively improving. If you can lend a hand, it would be very appreciated.

@flier
Copy link

flier commented Aug 7, 2017

@adriancole sure, let me check it later

@marqub
Copy link

marqub commented Jan 19, 2018

Is there some plan to filter or sample traces for zipkin?

@kyessenov what do you mean exactly? Sampling is already supported (only via runtime, can be trivially added to the config). What do you mean by filtering?

@mattklein123 , can you point me to a sample code or a documentation that shows how to configure these sampling options? Thx

@mattklein123
Copy link
Member Author

Here are the runtime settings: https://www.envoyproxy.io/docs/envoy/latest/configuration/http_conn_man/runtime

Work is ongoing to make these config settings also: #1813

@mattklein123
Copy link
Member Author

Closing this out as I don't think it's worth tracking the small items here anymore and we have several examples use Jaeger.

jpsim pushed a commit that referenced this issue Nov 28, 2022
We should be using bazelisk on CI since that's what we advise doing locally.

Signed-off-by: Michael Rebello <[email protected]>
Signed-off-by: JP Simard <[email protected]>
jpsim pushed a commit that referenced this issue Nov 29, 2022
We should be using bazelisk on CI since that's what we advise doing locally.

Signed-off-by: Michael Rebello <[email protected]>
Signed-off-by: JP Simard <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tracing enhancement Feature requests. Not bugs or questions. help wanted Needs help!
Projects
None yet
Development

No branches or pull requests

8 participants