grafana-google-stackdriver-datasource icon indicating copy to clipboard operation
grafana-google-stackdriver-datasource copied to clipboard

trying to use google stack driver

Open percival-el opened this issue 7 years ago • 5 comments

hello , I'm trying to figure out how to use the plugin , i'm confused here a bit . there might be a couple of steps missing , appreciate the effort .

Thanks

percival-el avatar May 24 '18 05:05 percival-el

also can't find google stackdriver plugin , on the grafana plugin page .

percival-el avatar May 24 '18 05:05 percival-el

@percival-el it isn't published yet. If you want to use it now, you'll have to install it by hand. Example below.

  • https://github.com/HumanCellAtlas/metrics/blob/master/Makefile#L69-L74
  • https://github.com/HumanCellAtlas/metrics/blob/master/Dockerfile#L6

Note: not all features are working yet.

mweiden avatar May 24 '18 05:05 mweiden

ok , Thanks . Is there a automated build on the docker store ?

percival-el avatar May 24 '18 06:05 percival-el

hi, I geting the following error while trying to build from dockerfile .

" COPY target/grafana.ini /etc/grafana/grafana.ini COPY failed: stat /var/lib/docker/tmp/docker-builder268304342/target/grafana.ini: no such file or directory " steps

  1. created a target directory , added the required grafana binaries
  2. extracted the zip file , but there seems to be no .ini file that has to be copied inside the docker images

let me know if i'm going wrong somewhere .

percival-el avatar May 24 '18 06:05 percival-el

@percival-el The lines I highlighted in those two files were all you need if you are not configuring grafana with a grafana.ini. Once you have pulled the plugin into a directory called target here is a simpler Dockerfile that should work.

FROM grafana/grafana:5.0.4

COPY target/grafana-google-stackdriver-datasource-master/dist/ /var/lib/grafana/plugins/grafana-google-stackdriver-datasource/

Honestly, given that this plugin is still in development, I think this thread is a bit off topic for this repo. What you have done is identified a need for better documentation. I would close this issue and just open another one asking specifically for documentation.

mweiden avatar May 24 '18 15:05 mweiden