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

Add a CLI tool to query a TSDB block #269

Open
fpetkovski opened this issue May 21, 2023 · 4 comments
Open

Add a CLI tool to query a TSDB block #269

fpetkovski opened this issue May 21, 2023 · 4 comments

Comments

@fpetkovski
Copy link
Collaborator

fpetkovski commented May 21, 2023

It would be great to have something like promql-cli that allows executing a query against a TSDB block. The main motivation for such a tool is to visualize CPU and memory usage by operator so that we know which computations are expensive. We could use time spent in operator and samples processed/produced by operator as proxies for these resources.

This issue is currently blocked by #106.

@yeya24
Copy link
Contributor

yeya24 commented May 25, 2023

Is this feature in the scope of this repo?

@fpetkovski
Copy link
Collaborator Author

My thought was that it can be useful for benchmarking and profiling queries. The CLI tool could output time spent in each operator, memory used by operator etc. So it should be more than a generic querying tool.

@yeya24
Copy link
Contributor

yeya24 commented May 29, 2023

The CLI tool could output time spent in each operator, memory used by operator etc

That's an interesting idea. Do we have those metrics built in this library now? We don't have a way to track time and memory usage now. Shouldn't we have that first before the CLI?

@fpetkovski
Copy link
Collaborator Author

fpetkovski commented May 29, 2023

Agreed, we would need #106 to be done first. I updated the description to have more clarity.

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

No branches or pull requests

2 participants