HeatMap: Sort y buckets when all bucket names are numeric

[leeoniya]

Fixes #60545
Fixes #65314

i don't think this is the proper solution, but it is an easy one that works.

i think we need to move away from handling every format at every level:

1. datasources (frontend bits)
2. transformers
3. panels

ideally panels have a single, pre-defined shape that they accept, and we auto-suggest and explicitly add the necessary transformers that get data into this shape. related: #64092, cc @grafana/data-plane-wg.

[github-advanced-security]

You have successfully added a new CodeQL configuration .github/workflows/pr-codeql-analysis-javascript.yml:analyze. As part of the setup process, we have scanned this repository and found 29 existing alerts. Please check the repository Security tab to see all alerts.

[nmarrs]

This solution appears to resolve this issue with correct sorting - though I am not confident on the direction in which we are displaying the sorted list (seems to make more sense to show low -> high along the y axis)

Testing this issue's dashboard locally it appears that this solution is not working. Are there additional query settings / transforms that need to be set in order for this solution to work in more cases?

[leeoniya]

though I am not confident on the direction in which we are displaying the sorted list (seems to make more sense to show low -> high along the y axis)

that debug panel has an explicit reverse configured:

Testing #60545 dashboard locally it appears that this solution is not working. Are there additional query settings / transforms that need to be set in order for this solution to work in more cases?

you're right. that dashboard has a response with multiple nameless frames that have time+value fields. i added more magic to make it work :(

[grafanabot]

The backport to v9.4.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-65322-to-v9.4.x origin/v9.4.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 6f4232bee383a7782ebbdcd31624f11a2d2bdfab
# Push it to GitHub
git push --set-upstream origin backport-65322-to-v9.4.x
git switch main
# Remove the local backport branch
git branch -D backport-65322-to-v9.4.x

Then, create a pull request where the base branch is v9.4.x and the compare/head branch is backport-65322-to-v9.4.x.

[npc203]

I'm still facing this issue, with the current main branch on my local instance

Just to be super sure, also checked whether I really have the commit in my history

Here's the paste from "get help"
debug-IO Size - async_write_ind-2023-04-17 00_51_23.json.txt

[leeoniya]

we expect either frame.name or frame.fields[1].name to be the bucket name. in your case, you only have frame.fields[1].labels.le set to the bucket name.

maybe take a look at the the influx queries in #60545 to see how to make sure the columns/fields contain the bucket names.

if you open a new issue with your previous comment/snapshot, we can discuss whether it makes sense for us to also probe frame.fields[1].labels.le.