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

TimeseriesToTable with multiple timeseries #88027

Open
mem opened this issue May 17, 2024 · 1 comment
Open

TimeseriesToTable with multiple timeseries #88027

mem opened this issue May 17, 2024 · 1 comment
Labels

Comments

@mem
Copy link
Contributor

mem commented May 17, 2024

Why is this needed:

I'm trying to find a way to visualize three dimensional data. My first two dimensions are categorical and my third dimension is time. This means I have N×M timeseries. Using a regular graph doesn't work (too much information). Using a table doesn't work (because of the time component). Using multiple rows doesn't work (too much vertical scrolling). Using repeating gauges doesn't work (repeat doesn't work with more than one dimension). Using repeating rows and repeating stat panels sort of works, but there's too much vertical scrolling, and it also makes it hard to scan along one of the dimensions.

What would you like to be added:

I have a (Prometheus) query that returns multiple timeseries. Unlike #76291, my case involves two labels. Something like server="1", region="x". What I would like to do is have a table where the cell type is sparkline, and each sparkline corresponds to one of those series. My first column is e.g. server, and the rest of the columns are x, y, z, etc. If I have an instant query, I can make this work with (multiple) transformations. I have not found a way to make this work with a range query.

Who is this feature for?

My hunch is that this is niche, but it might be because the feature doesn't exist yet. Having to visualize multiple dimensions in a compact format is not a super common problem, but it's also not that uncommon.

@grafanabot
Copy link
Contributor

@mem please add one or more appropriate labels. Here are some tips:

  • if you are making an issue, TODO, or reminder for yourself or your team, please add one label that best describes the product or feature area. Please also add the issue to your project board. 🚀

  • if you are making an issue for any other reason (docs typo, you found a bug, etc), please add at least one label that best describes the product or feature that you are discussing (e.g. area/alerting, datasource/loki, type/docs, type/bug, etc). Our issue triage doc also provides additional guidance on labeling. 🚀

Thank you! ❤️

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

No branches or pull requests

2 participants