Can not connect to data source
eronrunner opened this issue · comments
After starting the Grafana with Grafana-trino plugins:
- choose the Grafana plugins and click on Create data source Button
- choose the Data Source tab and change HTTP address and port: http://trino.query.com:8080
- Then save & test, but the test data source failed and shows the message
- After checking the URL to that the request fetched, the URL is always localhost:3000/api/ds/query instead of the URL http://trino.query.com:8080
I also create a dashboard with a panel using trino-datasource, and the query isalways failed and URL is localhost:3000/api/ds/query
I don't understand why but, please help me to check this. Appreciate it!
If the save & test
button fails, you can go into the explore
and it should show a more detailed error message there. Also, try checking Grafana logs for errors. You might have to set the GF_LOG_LEVEL=debug
environmental variable in the Grafana server to get more details from data source plugins.
The logs include a "plugin unavailable" error - this indicates the plugin process might have panicked. You really need to enable debug logs to see the panic stack trace from the plugin.
Which version of this plugin are you using? If you checked out the repository, which commit? Have you built everything, including running the mage
command?
I just noticed I haven't included the proper ZIP in the beta.1 release, so if you've used these artifacts get this one instead: https://github.com/starburstdata/grafana-trino/releases/download/v1.0.0-beta.1/trino-datasource.zip
hi, nineinchnick,
when i use this new plugin as your post here (https://github.com/starburstdata/grafana-trino/releases/download/v1.0.0-beta.1/trino-datasource.zip), i got a error when a a trino-datasource.
the error is : "this.getRef is not a function"
see the error picture as i attached.
Look forward to your help...
@zjeoff can you create a separate issue for this? Please specify which Grafana version you're using.
@nineinchnick sure , issue #39 has been submitted...
The logs include a "plugin unavailable" error - this indicates the plugin process might have panicked. You really need to enable debug logs to see the panic stack trace from the plugin.
Which version of this plugin are you using? If you checked out the repository, which commit? Have you built everything, including running the
mage
command?
Oh,
I check logs when building lib by mage
command, it might have somethings wrongs with go
version. So I re-build and then restart grafana container, and it's working.
Thank you, @nineinchnick!