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

Add more Opentracing detail to the app #3383

Merged
merged 2 commits into from
Oct 26, 2018
Merged

Add more Opentracing detail to the app #3383

merged 2 commits into from
Oct 26, 2018

Conversation

bboreham
Copy link
Collaborator

This lets you see much more clearly which parts of the processing are taking time.
Unfortunately we have to add a thousand context.Context parameters, but that can't be helped - this is the Go way.

I used reflection to get the name of Map and Reduce objects, to avoid typing in specific span calls in each of them.

The overall result can look like this (using Jaeger):

image

@2opremio
Copy link
Contributor

Can you fix the conflicts? Otherwise LGTM

This is useful for cancellation or tracing.
Also log things like number of nodes in Map, total number of reports.
Copy link
Contributor

@satyamz satyamz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@satyamz satyamz merged commit 3be8cf7 into master Oct 26, 2018
@bboreham bboreham deleted the opentracing branch January 13, 2020 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants