-
Notifications
You must be signed in to change notification settings - Fork 3
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
updates for grafana 6.6.x #2
base: master
Are you sure you want to change the base?
Conversation
kyleboyle
commented
Jan 30, 2020
•
edited
Loading
edited
- backend dep updates
- go grafana package dep updated
- gofmt golang backend
- suggested kairosdb url in grafana datasource
- grafana-kairosdb docker image with kairosdb datasouce installed
- updated readme with current build instructions
- backend dep updates - go package updates - gofmt bakend - suggested kairosdb url in grafana datasource - grafana-kairosdb docker image with kairosdb datasouce installed - updated readme with current build instructions
Nice work. I'll likely branch the current code to keep it for grafana 5 compatibility and then merge this one to master. |
@brianhks I noticed that the plugin does not currently implement a testDatasource() verification function which is suppose to test the validity of the ds connection configuration. Do you think a good verification procedure would be to to get the metric names or is there a no-op query that could be executed to test? |
Yes that is a good idea. I'd call /api/v1/health/check It returns a 204 if healthy and 500 if not. I think we added it specifically for load balancers to detect if Kairos is up and happy. |
Updated. I didn't make it verify specifically 204 vs 200 but that probably doesn't matter. |
@brianhks What else do I need to do to get this merged. It seems people are starting using my branch instead off official, which is bad. |
Hi @kyleboyle, I tried to build kairosdb-datasource plugin from your branch but got this error:
I have followed steps from ReadMe file but can't build backend yet. ENV info:
Can you check it, please ? |
Found the problem. After installing
As I understood it's limited to 6.6.x as minimal supported version. So, I'll upgrade Grafana to latest and then will test again. Hope this will work finally because we really need KairosDB as datastore for Grafana. |
@mr-yaky If you are just looking to use it, everything is already compiled and committed under "dist". I'm hoping my branch will be merged soon so that these source path issues are not confusing. |
Yes, thank you. But I was need to compile backend for using on Alpine Linux (musl library). So, because that I have recompiled it. |
Ok sounds good. Based on your error message I think you should have cloned it to a go path .../grafana/kairosdb-datasource/ and not .../kyleboyle/kairosdb-datasource |
Hi @kyleboyle, I have updated to 6.6.1 Grafana version but still get the same problem: I use official grafana docker image and put plugin to following directory:
I tried also to copy already compiled dist files from your git repo but unfortunately got the same. |
@mr-yaky Here is a baseline test that works: git clone https://github.com/kyleboyle/kairosdb-datasource.git
cd kairosdb-datasource
docker run -d -p 3000:3000 -v $(pwd)/dist:/var/lib/grafana/plugins/grafana-kairosdb-datasource --name grafana grafana/grafana:6.6.1 |
@kyleboyle Yes, you are right. I have tried to use other path and when I put this plugin exactly to /var/lib/grafana/plugins it has started working. Thank you! I hope this PR will be merged finally. |
Start with setting up the go workspace and provide detailed installation procedures. I am having difficulty installing with a wiki manual. I need your help. -- my env-- |
@kopenslsb If you are just looking to use it, everything is already compiled and committed under "dist". There is no reason to build the go plugin. If you are looking to make changes to the go plugin you should already know how to set up a working build env. |
My grapana is installed somewhere other than the default installation directory. |
@kopenslsb grafana loads plugins from its plugin directory. You will need to copy this plugin to that location. |
Any update on this PR? |