You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the template variable UI is quite limited and makes it much more difficult to develop queries compared to the normal query editor. A failed query does not give any indication on the output. Simply the results stop getting updated.
Also getting the actual SQL query with all the macros unrolled requires going to the query log to get something that can be pasted into the CLI for testing.
Getting template queries right is IMO even more important than individual panel queries because a bad template variable query can prevent the whole dashboard from loading.
So some things that could be improved in order of priority. I understand if some of these can't be realistically implemented due to the framework limitations.
Displaying the appropriate error when a query fails
Having a simple SQL query inspector to at least see the formatted query. The output JSON would be nice but not really absolutely necessary
Now that we there is default timeseries column name it should be possible to also use the $timeFilter macro in template variables, right?
Having some progress indicator that shows when a query is active in the editor
Automatically adding a comment to the query indicating the dashboard and possibly also the user ID, similarly to what is done in the normal panel queries. It would be helpful to also have some indication that this query is a template variable (and even the template variable name, if possible)
The text was updated successfully, but these errors were encountered:
Currently the template variable UI is quite limited and makes it much more difficult to develop queries compared to the normal query editor. A failed query does not give any indication on the output. Simply the results stop getting updated.
Also getting the actual SQL query with all the macros unrolled requires going to the query log to get something that can be pasted into the CLI for testing.
Getting template queries right is IMO even more important than individual panel queries because a bad template variable query can prevent the whole dashboard from loading.
So some things that could be improved in order of priority. I understand if some of these can't be realistically implemented due to the framework limitations.
The text was updated successfully, but these errors were encountered: