How works Prometheus Integration ? #169
Labels
documentation
Improvements or additions to documentation
prometheus
question
Further information is requested
Comments
|
Hi @SckyzO, Helene |
|
Hello @Helene Ok, I understand :) This will definitely be a good feature :) Do you know when a final version with official Prometheus support will arrive? I would like a "docker/podman" version even in beta. I have to implement it for a client and I would like to start working on the subject. I understood how it worked but in container mode it is not yet supported (I adapted the dockerfile but there is still work). The problem is that I am on a closed network, so the python pip offline part must be managed offline. I would therefore prefer to make it work with containers :) Tom |
|
Hi @SckyzO, Your early feedback would be greatly appreciated. |
Helene
added
documentation
|
Hello Helene. I can't run my container, I have many error with cherry and certificate : For example : And, if we use container with certificate, why do not add certificate directly in the container ? It is a localhost self-signed certificate I continue to debug :) I don't know why, I started my container one time, but after kill and re-run container, it never restarted ... Another question, I have to recover mmsdrfs, but in my case, you have to add hardware gradually to my ESS architecture, so I think that this file should be passed as an argument (mount a local path with this file I think) , because I will have to rebuild the container if my architecture evolves. |
|
Juste for information, my container is started, i always have "ssl error" as said in my previons comment, but it working. In log, I have many Warnings Like this : I don't know why and how to check this warnings ... If you have an idea :) |
|
Oh, I found in code the list of all endpoints :) Maybe you should update Prometheus Readme with this list :) @Helene very good job pour this prometheus integration development |
|
Hello @SckyzO , The ssl exception you are seening is comming from CherryPy application. It is known issue. Finally it has been fixed 2 weeks ago but not published yet from CherryPy development team. You can follow on this
That is correct your local folder, where you mount the grafana-bridge logs, need to have write permissions, otherwise the log files could not be updated. Are you running grafana-bridge container on baremetal or on a kubernetes cluster. On kubernetes you can make the installing process much easier using deployment script.
This is a good point. Mounting mmsdrfs/ZIMonsensors.cfg file would make sense. Please open for this a separate issue. I'm a little bit worry about the messages Are you using the latest grafana-bridge code? Also verify your prometheus config file prometheus.yaml has a correct job definition
Yes the endpoints need to be documented. I'm still working on documentation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello team,
I see that IBm bridge for grafana support promtheus.
It is possible to explain how it is working (update readme maybe) ? And how to use it ?
And can you update your dockerfile to use Prometheus Exporter API ?
Regards,
The text was updated successfully, but these errors were encountered: