-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Query variables stopped working with 0.4.0 #230
Comments
Can you provide some details? What you've tried and what happened?
Have you read release notes? IIRC variables support querying fully the
datasource as we'll now since 0.4.
…On Wed, Feb 16, 2022, 22:08 silentZaika ***@***.***> wrote:
After upgrading to the plugin version 0.4.0 with Grafana 8.3.6 (and
8.3.5), the query variable are not populated from JSON datasource.
—
Reply to this email directly, view it on GitHub
<#230>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACQAJMETYNCRAMLODLRI4TU3QG3ZANCNFSM5OSY45RQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Well, I had a query variable working with JSON datasource, returning an array of strings. After the plugin upgrade, it stopped working, just had "None". |
Working with variables changed since 0.4. Have you checked release notes? Can you provide some details, what are of strings do you expect? |
I checked release notes, but they don't mention what exactly changed. |
Variable query calls |
Oh, sorry. I didn't specify it. I have the setup as described in the documentation for |
But variables now call query, same as panels do. It allows more
flexibility.
…On Thu, Feb 17, 2022, 20:02 silentZaika ***@***.***> wrote:
Oh, sorry. I didn't specify it. I have the setup as described in the
documentation for /search here
https://github.com/simPod/GrafanaJsonDatasource/tree/0.4.0#search
—
Reply to this email directly, view it on GitHub
<#230 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACQAJJGGAYEIJWESU4CP3LU3VA27ANCNFSM5OSY45RQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
Well, it might be more flexible, but why fix something that has not been broken) |
Search works for listing all metrics
Variables had single use case in v0.3 - listing all metrics.
Now it has been improved to have infinite use cases by allowing to return
any data based on any arbitrary input.
…On Thu, Feb 17, 2022, 20:47 silentZaika ***@***.***> wrote:
Well, it might be more flexible, but why fix something that has not been
broken)
Also, the documentation suggests that /search still works.
—
Reply to this email directly, view it on GitHub
<#230 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACQAJJBZ7H56R2L6U262WLU3VGDFANCNFSM5OSY45RQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
I've edited release notes to include information about variables calling another endpoint. Thanks. |
My bad, it calls |
After upgrading to the plugin version 0.4.0 with Grafana 8.3.6 (and 8.3.5), the query variable are not populated from JSON datasource.
The text was updated successfully, but these errors were encountered: