-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Interval variable is not passed through anymore #144
Comments
Can you open devtools Console and see if there's a warning about Interval type not being supported? |
Indeed I receive "Variable of type "interval" is not supported" at DataSource.ts:198 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please kindly keep this issue open. |
There's a bug in stale bot that does not remove |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
An anti-stale-bot message. Thx |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Dear SimPod Team,
I raised the following issue at Grafana gihub (grafana/grafana#30785). According to them, I shall report this issue here.
What you expected to happen: Interval variable and its selected value is submit to API via scopedVars
How to reproduce it (as minimally and precisely as possible):
Add simpod-json-datasource as datasource.
Add a new Dashboard
Add a new Variable with Type "Interval" to the dashboard, you may use the default list that is beeing provided.
Save
Refresh Dashboard
Capture API data via Fiddler.
Note that the variable is not present in scopedVariables anymore.
Anything else we need to know?:
Environment:
Behavior 6.4.4 vs. 7.3.7 and Workaround:
Best Regards
Krisztian
The text was updated successfully, but these errors were encountered: