-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
Allow re-ordering of columns in table panel configuration #5082
Comments
+1 |
I agree. It would be nice to be able to reorganize the columns. |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
indeed +1 |
+1 |
With Prometheus data sources there is no way that I can tell to reorder columns, not even editing the JSON. |
Strange , means Prometheus returns them in random order (I think) |
@torkelo Well, prometheus labels are being turned into columns and labels have no inherent ordering, so that's to be expected. |
+1 |
is there any progress? |
+1billion to this, a prometheus data source results in columns being displayed in a non-deterministic order which is bloody well rubbish! :) It'd be great if grafana could control this |
+1 This is especially painful when trying to use Prometheus, as previous commentators mentioned. |
Is there any progress??? This is a MUST have feature, right now you have no control over the table which is ridiculous. |
+1 |
+1
|
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
sry but here is another +1 ... |
I think this feature is very useful. +1 |
this is a needed feature!! +1 |
+1 |
:shakes_fist: |
yes for influxdb when dealing with tags, the order of columns is imposed by the alpha-numeric order. |
+1 |
For people using Prometheus, I have the world's ugliest hack to get around this. Suppose I have a query $QUERY that returns vectors with labels $A_LABEL, $SOME_LABEL, and $THIS_LABEL. In my table, I will see the columns in this same order, since I listed them alphabetically. However, I want the order to be $SOME_LABEL, $A_LABEL, $THIS_LABEL. We can use Prometheus's
Pretty dumb, right? But it works. Unfortunately, these are ugly names to read, so let's reformat them. Add a column style that matches the regular expression The fact that this is necessary is ridiculous. Column ordering should really be a built in feature. So, you know, +1. |
+1 |
To solve this issue, i ussed a custom backend using the json data source plugin https://grafana.com/plugins/simpod-json-datasource. |
+1 |
I would like this as well |
This would be a great feature |
+1 |
FYI - the work around to this bug is to edit the panel json directly. Look for the columns block then move the column definition around in the json. (panel dropdown --> more --> Panel Json)
|
@WilliamLHarms That only works for some data sources. Prometheus for example builds the columns dynamically, there is no JSON to edit. |
@paol - yea, it was an elastic datasource. I guess there isn't a work around for the bug. Just scrap your panel and start over. |
We are all waiting for the hero who will apply this feature. |
This would be a great feature to have. |
Would love to be able to do this as well. |
I'd like to see that feature realised. |
The feature will improve the user experience greatly. |
Prometheus sort the labels attributes by alphabetic order. Not randomly. If you have the labels: "hostname", "ip", "cluster", the order will be:
But if one label name begins by capital letter the order change.
If you want to sort the labels, you can use the |
+1 and btw if the amount of columns is to high, the header row is stuck and not able to scroll with the rest (#4157) |
+1 Why not order on the Column styles order and make them, easy to move so you can drag them on the screen. |
@torkelo I still see this is not yet fixed. Using the grafana version 6.7.2. |
Coming in 7.0 via the new transform tab! |
it worked for me with 20 columns thank you |
There currently is no way (other than editing the JSON) to re-order existing fields in a table panel. This is pretty painful, if you have a lot of columns, in particular, if there is no auto-completion.
The text was updated successfully, but these errors were encountered: