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

Grafana variables rewritten as absolute numbers when scenes are enabled #271

Open
llamafilm opened this issue Nov 1, 2024 · 2 comments
Open

Comments

@llamafilm
Copy link

llamafilm commented Nov 1, 2024

Using this plugin in Grafana 11.3.0, the time range variables are sometimes changed to absolute time stamps. This screen recording shows it happening after I duplicate the panel, but that's not the only event that causes it; it also happens sometimes after editing a panel or just refreshing the page.

This problem can be avoided by modifying the Grafana config file like this:

[feature_toggles]
dashboardScene = false

I'm using the plugin build from #268. Unfortunately I don't have a way of testing this with the release version, but I don't think the changes in that PR are relevant here.

The specific query does not matter but here is one example:

SELECT count(*) AS count
FROM prodhive.bdp.particle_google_meet_hardware
WHERE time_usec/1000 >= ${__from} AND time_usec/1000 <= ${__to}
AND event_type = 'ISSUE'
AND dateint > 20241030

Notice in the video, the third line of the query is turned into WHERE time_usec/1000 >= 1730475970811 AND time_usec/1000 <= 1730479570811, and after this happens, changing the time range has no effect.

grafana.trino.bug.mov
@llamafilm llamafilm changed the title Grafana variables are rewritten as absolute numbers Grafana variables rewritten as absolute numbers when scenes are enabled Nov 1, 2024
@nineinchnick
Copy link
Member

Could this be a Grafana issue, not an issue with this plugin? I don't even know what Dashboard Scenes are.

@llamafilm
Copy link
Author

I discussed this with Grafana support via email and they think it's a bug in the plugin because they were unable to reproduce it with other SQL data sources.

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

No branches or pull requests

2 participants