-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
100% sampling, aka firehose mode (mostly storage affecting) #1869
Labels
Comments
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 9, 2018
This starts towards "firehose mode" by making it possible to disable indexing, notably on cassandra where SASI amplifies writes into the cluster. When enabled, only retrieval by ID is allowed. That said, someone can feel free to run the dependency linker if they like.. If 100% sampling is on, the dependency links will relate to actual service calls made. See #1869
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 10, 2018
This starts towards "firehose mode" by making it possible to disable indexing, notably on cassandra where SASI amplifies writes into the cluster. When enabled, only retrieval by ID is allowed. That said, someone can feel free to run the dependency linker if they like.. If 100% sampling is on, the dependency links will relate to actual service calls made. See #1869
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 12, 2018
This starts towards "firehose mode" by making it possible to disable indexing, notably on cassandra where SASI amplifies writes into the cluster. When enabled, only retrieval by ID is allowed. That said, someone can feel free to run the dependency linker if they like.. If 100% sampling is on, the dependency links will relate to actual service calls made. See #1869
Current status: As of latest version, |
codefromthecrypt
added
enhancement
collector
storage
Group label for Storage components
labels
Oct 23, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
to be fleshed out: this would be a mode that has more impact on tracers and transports than the server. That said, a 100% mode likely means less or no indexing on storage side, with a short (like 1hr) retention. There could be UI support at least fetch by ID which could query both the normal sampled storage and a firehose one, or it could be considered different apps. These details will be added and refreshed into a revised description with a plan.
The text was updated successfully, but these errors were encountered: