search

sipcapture / homer7-docker

HOMER 7 Docker Images
92 stars 84 forks source link

homer-app - issue with displaying grafana metrics via widget #97

Closed mikemeehan203 closed 3 years ago

mikemeehan203 commented 3 years ago

When using a vanilla hom7-prom-all build I cannot get any grafana metrics to appear in the homer dashboard. Below are the steps I'm taking. Thanks.

(1) Update the host address, using an IP, instead of "grafana"

01

(2) Add a new dashboard

02 03

(3) Add a grafana metrics widget

04

(4) Select the dashboard and panel **the fact that I can select the dashboard and panel tells me the communication between homer-app and grafana exists.

05 06

(5) The widget fails to successfully talk to the grafana instance.

07

(6) That same dashboard can successfully be viewed when logging into grafana

08

Please let me know if you need anything else to help troubleshoot the issue. Thank you in advance.

lmangani commented 3 years ago

Hello @mikemeehan203 this is a network issue - could you check what the network tab of your browser reports and which URL its trying to load?

mikemeehan203 commented 3 years ago

Hi @lmangani, yes, here's what I've got -

Initiator

Info

chrome_01

chrome_02

It's worth noting, that this is a remote system I am access on the Internet, I'm not running it on my laptop. When port forwarding to the above URL's (firewall access to port 3000 is not open from my laptop) I can see the intended graphs being requested, albeit I have no call volume at the moment.

port_forward_attempt_1 port_forward_attempt_2

Thanks, Mike

lmangani commented 3 years ago

Have you created and configured an API access token from grafana or are you using the fake authentication?

mikemeehan203 commented 3 years ago

Hi @lmangani,

I'm using an API access token from grafana. As a test to make sure access is granted, if I were to change that access token to something invalid, the dashboards loaded into Grafana would not populate. See (4).

Thanks, Mike

lmangani commented 3 years ago

@AlexeyOplachko do you see anything out of the ordinary here?

AlexeyOplachko commented 3 years ago

This problem used to happen if you had UI on localhost and API on remote, but from what I've checked rn it isn't happening after we switched our approach to Grafana widget.

lmangani commented 3 years ago

@mikemeehan203 please describe step by step how you are configuring the widget from scratch. let's see where it happens.

kvrudenko commented 3 years ago

The same problem. In homer-webapp container I have this message: {"time":"2021-07-25T00:33:17.267260218+03:00","level":"ERROR","prefix":"echo","file":"proxy_1_11.go","line":"20","message":"remote http://grafana/ unreachable, could not forward: dial tcp 172.18.0.3:80: connect: connection refused"} Why app tries connect to port 80 ? Grafana published on port 3000 and the settings the same as @mikemeehan203 showed.

kvrudenko commented 3 years ago

Гомер нормально в виджете видит все дашборды в графане, развёрнутой в соседнем контейнере, но почему-то запрос на отображение делает не на тот порт, который указан в конфиге виджета.

McSimDP commented 3 years ago

Same problem. In Chrome console: "Refused to display 'http://10.10.0.9:3000/' in a frame because it set 'X-Frame-Options' to 'deny'."

lmangani commented 3 years ago

@McSimDP easy to google this up and see its not related to our project:

https://grafana.com/docs/grafana/v7.5/administration/configuration/#allow_embedding

McSimDP commented 3 years ago

@McSimDP easy to google this up and see its not related to our project:

https://grafana.com/docs/grafana/v7.5/administration/configuration/#allow_embedding

Thanks, helped