✨ Support Grafana 10.4

[JosefWN]

Hi, it's been a couple of years since these dashboards received some love. Tried to bring them at least somewhat up to par with the latest versions of Jitsi/Prometheus/Grafana. Tested with jitsi-helm master (running stable-9364) and kube-prometheus-stack 58.0.0 (running Grafana 10.4).

Is it worth maintaining two almost identical charts? Could we just go with "Jitsi & System" perhaps?

Fixes:

• Fix typo in panel name & legend "Audo/videochannels" -> "Audio/video channels"
• Fix typo in panel name "Videostreams" -> "Video streams"
• Consistent casing in panel names & panel groups
• Add dashboard tag "jitsi" to both dashboards
• Fix deprecation: This plugin uses a deprecated, legacy platform based on AngularJS and will stop working in future releases of Grafana. https://grafana.com/docs/grafana/latest/developers/angular_deprecation/
• Add missing "Videobridge stress level" to "Jitsi" chart (aligning with "Jitsi Meet & System")

Possible issues remaining:

• With 3 people in a room, two with webcams on, I get "0 videostreams" consistently, is this intended? Is the metric broken?
• "CPU busy", "Used RAM memory" and "Transfered data volume" are all "No data", perhaps I'm missing something?

[0x46616c6b]

Thank you for the contribution! I will try to review your changes as soon as possible and provide feedback.

[0x46616c6b]

LGTM 👍

The dashboard "jitsi-meet-system" contains metrics from node-exporter. So, this only makes sense if you also have these exporter metrics available.

[0x46616c6b]

Both Dashboards are updated at grafana.com/dashboards

[JosefWN]

@0x46616c6b Yes, I have the node exporter up and running, but the instance in the dropdown in the dashboard, which is obtained from the metric jitsi_conferences's instance label, corresponds to the Kubernetes-internal JVB pod IP, whereas the instance label on the metric node_cpu_seconds_total for example, is referring to the node IP.

I suspect it could be the JVB_WS_SERVER_ID which is determining the value of the exported metric label, which by default is set to the JVB pod's IP using, for example, jitsi-helm. I suppose this touches a bit on #116 as well, although I currently only have one videobridge.