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

Do not export zipkin exporter calls to zipkin endpoint #167

Merged
merged 3 commits into from
Jul 30, 2019

Conversation

lmolkova
Copy link

@lmolkova lmolkova commented Jul 30, 2019

Fix #164 #134 #108

This is temp fix, we should do #166 to fix it permanently

@lmolkova lmolkova merged commit b94fc10 into master Jul 30, 2019
@lmolkova lmolkova deleted the doNotExportZipkinCalls branch July 30, 2019 17:56
if (shouldExport)
{
var zipkinSpan = this.GenerateSpan(data, this.localEndpoint);
zipkinSpans.Add(zipkinSpan);
Copy link
Contributor

Choose a reason for hiding this comment

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

@lmolkova I might be reading the code incorrectly, but there appears to be a possibility that SendSpansAsync can be called with an empty span list, resulting in a HTTP call to Zipkin, which still causes a invisible loop.

Copy link
Author

Choose a reason for hiding this comment

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

@johnduhart sorry, this is merged already...

Would you mind sending very short PR to return from ExportAsync immediately if Span batch is empty?
It seems it should not ever happen (but seems to be reasonable anyway), see here:

if (this.spans.TryTake(out var item, this.scheduleDelay))

And also after loop runs we should make sure zipkinSpans are not empty.

Copy link
Contributor

Choose a reason for hiding this comment

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

And also after loop runs we should make sure zipkinSpans are not empty.

This was my main concern, given we're selectively including spans in this method.

Sure, I'll cut a PR to add that.

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.

Zipkin exporter http calls get exported themselves
3 participants