While looking for icinga2 grafana api examples, I found an reference to grafana.ini and “allow_embedding = true” . That seemed to do the trick but now you made me curious and I want to find out how to get this api access working
For now I created a API key in grafana and changed the configuration in icinga2 to indirect proxy and set the api key in there. Still investigating, but for now I get an internal server error 500 in icinga2.
It’s showing that I’m missing something but I’m lost…hope you have another hint.
Tried another thing that was used here and it’s called Modify Header info chrome extention. Filling in the api key like describes shows me that I can see the graphs in grafana using the api key… So in my eye’s there must be something wrong with Icinga not using the authentication header api key to retreive the graph ?!
I think there are the fonts missing, can you check the syslog for any messages from grafana while view a host/service object and also watch syslog during startup of grafana. The message you posted shows that grafana has problems to load something during renderer run.
Update - Sept 2019 - I am currently building a new RPI4 unit and found that the compile will fail. This seems to be due to the Google Remote Procedure Call (grpc) not working on Buster/RPI4. Will update when this changes.
Reaction from a thread github thread
Tried the suggestion but doesnt work. Think it for now not possible to render on rpi and thus use a API key to get graphs in Icinga.
Seems like pre-built binaries for grpc v1.11.3 on arm are not available, only arm64. Not sure that there are prebuilt grpc node binaries at all for arm. I don’t currently have an arm device so hard for me to help out.
Seems like the only way is to build it from source and looking at your error seems like it tries to compile it but fails. Maybe your lacking some dependency like node-gyp and/or C++ build tools?