Create new grafana dashboard based on 11925

[titansmc]

https://grafana.com/grafana/dashboards/11925

[towolf]

Hi, I've made this. If you want any adjustments, I can touch it up more.

[titansmc]

@towolf That is fine to me, I was just wondering if it makes sense to upload the dashboard you have in this repo.

Cheers.

[towolf]

Dunno, some people prefer simpler dashboards. I like to have more detail. Because, you never know.

[MiningPickaxe]

I had issues with that grafana dashboard, most querys don't match (at least with the docker image of the jitsi-prom-exporter).
For example: largest_conference{instance = $instance} had to be largest_conference{app="jitsi",jvb_instance= $instance} in my case.
The extraction of the variable didn't work either, I havent fixed that yet

[towolf]

Hi @MiningPickaxe
You're right that largest_conference has a jvb_instance in its labels:

# curl -s 10.6.28.11:8999/metrics | grep largest 
# HELP largest_conference The current number of participants in the largest conference
# TYPE largest_conference gauge
largest_conference{app="jitsi",jvb_instance="jvb"} 0

But then, once its ingested in Prometheus there's also an instance label:

And that one refers to the host from where the metrics were scraped from.

And on the dashboard the $instance is grabbed like this. So I don't know why that doesn't work for you:

[MiningPickaxe]

Hi @towolf
could you maybe share your prometheus config related to this jitsi-prom-exporter?

[towolf]

@MiningPickaxe since we are running this standalone I just configured a static config for Prometheus:

# cat /etc/prometheus/jobs/static/jitsi.yml
- targets:
    - '10.6.28.11:8999'
  labels:
    job: "jitsi"
    instance: "h7020.example.com"

EDIT:
Ah, now that I'm actually looking, we are adding the instance label ourselves ... 🤦

[MiningPickaxe]

Ah ok :) Makes more sense now.
Once the jitsi-prom-exporter uses MUC Nicknames instead of Usernames (which would allow for monitoring multiple bridges) and passes that over to prom, it would be nice to be able to filter through those. But that will probably be implemented SOON™