-
Notifications
You must be signed in to change notification settings - Fork 38
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
Redis Datasource Plugin Failing Health Check on Grafana #71
Comments
Hello @WPS63, thank you for submitting the issue. What platform do you use? Could you please take a look at Grafana log files and send me an error. It does not look like a Redis error, more like a communication error between Grafana and Plug-in. |
Hi Mikhail, t=2020-10-08T13:01:57-0400 lvl=eror msg="Plugin health check failed" logger=context userId=1 orgId=1 uname=admin error="Failed to check plugin health: Health check failed" remote_addr=[::1] t=2020-10-08T13:01:57-0400 lvl=eror msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/api/datasources/5/health status=500 remote_addr=[::1] time_ms=67 size=40 referer=http://localhost:3000/datasources/edit/5/ |
@WPS63 Raspbian OS is 32bit and unfortunately, 32bit ARM Linux executable is not included in the release 1.2.0 available in the Grafana repository. I just built the master with 32bit ARM Linux executable for you: https://github.com/RedisTimeSeries/grafana-redis-datasource/archive/feat/71-arm.zip |
It worked perfectly. Thank you very very much, sir. |
@WPS63 Thank you for the update. Please let me know if you need anything else. |
Summary
I am trying to connect my Redis server to Grafana using the plugin and am getting a plugin health check failure message when I try to save and test my datasource.
Relevant information
My Redis server is running locally on the default localhost and port(127.0.0.1:6379.) I have installed the plugin and can see it on my list of available plugins on the Grafana dashboard as well as through the grafana-cli command. I have tried many url combinations(such as localhost:6379/0, http://localhost:6379, 127.0.0.1:6379, etc.) and had no luck. Here is an image of the dashboard page that is causing the issue:
Thanks in advance for your help and guidance.
The text was updated successfully, but these errors were encountered: