-
Notifications
You must be signed in to change notification settings - Fork 719
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
Support "firehose mode" #557
Comments
This was referenced Jul 21, 2018
codefromthecrypt
pushed a commit
that referenced
this issue
Aug 1, 2018
Performance is great, but implications of mutability should be top-level. This renames SpanRecord back to MutableSpan, as it focuses on the important thing. See #557
codefromthecrypt
pushed a commit
that referenced
this issue
Aug 1, 2018
Performance is great, but implications of mutability should be top-level. This renames SpanRecord back to MutableSpan, as it focuses on the important thing. See #557
(TraceContext, MutableSpan) will be the primary input for firehose handlers, whether they are metrics or service aggregators, or a secondary zipkin instance. There will be another flag that will determine if we record regardless of the primary sampling status. Stay tuned. |
finally got focus time on firehose #791 |
#796 < README |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Full description pending, but this will describe a mode where brave collects data regardless of sampling decision. At the point where spanReporter is used today, a branch will occur where "firehose" reporter gets all spans, and the existing one, only sampled ones. This is in support of aggregators such as span metrics.
Coming out of #529
The text was updated successfully, but these errors were encountered: