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

Downsampling in query service? #2727

Closed
yurishkuro opened this issue Jan 13, 2021 · 3 comments · Fixed by #2782
Closed

Downsampling in query service? #2727

yurishkuro opened this issue Jan 13, 2021 · 3 comments · Fixed by #2782
Assignees
Labels

Comments

@yurishkuro
Copy link
Member

It seems we have the wrong scope of these flags, what meaning do they have for the query service?

$ SPAN_STORAGE_TYPE=memory go run ./cmd/query help
...
      --downsampling.hashsalt string               Salt used when hashing trace id for downsampling.
      --downsampling.ratio float                   Ratio of spans passed to storage after downsampling (between 0 and 1), e.g ratio = 0.3 means we are keeping 30% of spans and dropping 70% of spans; ratio = 1.0 disables downsampling. (default 1)
...
@jpkrohling
Copy link
Contributor

I can schedule some time to track this down.

@jpkrohling jpkrohling self-assigned this Jan 14, 2021
@joe-elliott
Copy link
Member

The query service adds storageFactory flags here:

storageFactory.AddFlags,

which adds the downsampling flags here:

func (f *Factory) AddFlags(flagSet *flag.FlagSet) {

A quick git blame suggests it has been this way for years. We could split these methods into AddReaderFlags and AddAllFlags? If that makes sense I'll submit a PR.

@yurishkuro
Copy link
Member Author

We could split these methods into AddReaderFlags and AddAllFlags

+1

However, when archive storage is configured query can also write

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants