Grafana stats not working

Grafana Configuration
1

Hi,

We are having jitsi-meet instance hosted on AWS ec2 instance. We are also having Grafana Server which is on AWS ec2 instance.
We are not able to access Stats of jitsi-meet instance on Grafana server though Firewall is turned off. We have configured Grafana correctly, but still getting following errors:
curl -v http://X.X.X.X:8080/colibri/stats

  • Trying X.X.X.X…
  • TCP_NODELAY set
  • connect to X.X.X.X port 8080 failed: Connection refused
  • Failed to connect to X.X.X.X port 8080: Connection refused
  • Closing connection 0
    curl: (7) Failed to connect to X.X.X.X port 8080: Connection refused

If someone help me on this will be appreciated.

Regards,
Subodh

2

Hi,

Anyone is having solution.

3

You said:

curl: (7) Failed to connect to X.X.X.X port 8080: Connection refused

So, what does “netstat -lptn” show on that machine?

Is anything actually listening on address X.X.X.X port 8080?

Antony.

4

On Grafana server, I have fired command and output as follows:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 670/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 869/sshd
tcp 0 0 127.0.0.1:8088 0.0.0.0:* LISTEN 817/influxd
tcp6 0 0 :::8086 :::* LISTEN 817/influxd
tcp6 0 0 :::22 :::* LISTEN 869/sshd
tcp6 0 0 :::3000 :::* LISTEN 816/grafana-server

5

Hi Antony,

Any luck on this?

Regards,
Subodh

6

Well, your output of netstat shows that nothing is listening on any address on
port 8080, therefore it’s not surprising that Grafana is complaining that it
cannot connect to it.

Er, you did run this command on the machine with IP address X.X.X.X, I hope?

Beyond that, I can’t say what your problem is - given that you seem to be
expecting jitsi-meet to be offering these stats on port 8080, and it clearly
isn’t (in fact I do not see a Jitsi service listening on any port, so I
wonder how it is working at all), I suggest that you’re better off
investigating this with the Jitsi support people rather than Grafana, since
there clearly isn’t anything available for Grafana to work with.

If they come and back tell you that this really is a Grafana problem, by all
means come back with some details and someone may be able to help.

Regards,

Antony.

7

Hi Antony,
Thanks for your response.
We are able to access Grafana Dashboard with old release of Jitsi-Meet but with their latest version, we are getting port 8080 connection refused error though port is open in Firewall.

Regards,
Subodh

8

All I can say to that is that the current version of Jitsi-meet doesn’t appear
to listen on port 8080, therefore you cannot monitor it in the same way as the
old version.

I suggest asking for more assistance on the Jitsi list.

Regards,

Antony.

9

Hi Antony,

I have already raised this with Jitsi-meet and waiting for their response.

Will share with you once I get response from them,

Regards,
Subodh

10

Hi Antony,

Just one thought, can we change Grafana port 8080 to something else to access Stats of Jitsi.

If yes, where we can make change?

Regards,
Subodh

11

How have you currently configured Grafana to connect to Jitsi?

I wouldn’t know how to join these two things together without using some
intermediate data collection application.

Antony.

12

Hi Antony,

See below url- https://community.jitsi.org/t/how-to-to-setup-grafana-dashboards-to-monitor-jitsi-my-comprehensive-tutorial-for-the-beginner/38696

This is the link which I followed.

Regards,
Subodh

13

So, you are in fact using telegraf to collect data from Jitsi and place it
into Influxdb, which Grafana can then work with.

If telegraf needs to collect the data from Jitsi on a port other than 8080,
you would change this in the file /etc/telegraf/telegraf.d/jitsi.conf

Antony.

14

Hi Antony,

I did change port in telegraf like 8081, and make port 8081 in Firewall of Jitsi Server.

Error as follows:

curl -v http://18.X.X.X:8081/colibri/stats

  • Trying 18.X.X.X…
  • TCP_NODELAY set
  • connect to 18.X.X.X port 8081 failed: Connection refused
  • Failed to connect to 18.X.X.X port 8081: Connection refused
  • Closing connection 0
    curl: (7) Failed to connect to 18.X.X.X port 8081: Connection refused
15

You cannot just tell telegraf to connect to any port number you like. That
would be like arbitrarily thinking up a telephone number and trying to contact
a friend by simply dialling it, without checking whether it is their number.

You have to tell telegraf to connect to the port number which Jitsi is
listening on, and from the netstat output you posted yesterday, Jitsi is not
listening on any ports at all - if it were, the name “jitsi” or similar would
have appeared in the final column of the netstat output.

I did ask a question about this, and it would be helpful if you gave the
answer - did you run that netstat command on the machine you believe Jitsi is
running on?

If not, please do so.

If you did, can you see Jitsi running in the output of “ps ax” or similar?

Antony.