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

Track data usage across tenant / system #3572

Closed
bwplotka opened this issue Dec 11, 2020 · 2 comments
Closed

Track data usage across tenant / system #3572

bwplotka opened this issue Dec 11, 2020 · 2 comments

Comments

@bwplotka
Copy link
Member

We don't actually have any way to track what % of samples or overall data is ever queried, do we? Or does something mark blocks as they're ready to know usage?

Currently, we don't have this statistic in our system but would be nice to do the first step in this direction.

AC:

  • Allow tenant / system owner to answer question: What data is used/queried the most?

I think first is to also define the granularity of this information. I don't think the sample makes sense, but something like those most used matchers / query and the most used time range would be definitely nice to get. In some form of a histogram

@kakkoyun kakkoyun changed the title querier: Track data usage across tenant / system Track data usage across tenant / system Feb 1, 2021
@stale
Copy link

stale bot commented Apr 7, 2021

Hello 👋 Looks like there was no activity on this issue for the last two months.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

@stale stale bot added the stale label Apr 7, 2021
@stale
Copy link

stale bot commented Jun 3, 2021

Closing for now as promised, let us know if you need this to be reopened! 🤗

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

Successfully merging a pull request may close this issue.

1 participant