-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prometheus instrumentation to get metrics of the switchboard #96
Comments
I found out about agones via the XREngine project. |
To be clear, for agones, this is mainly to scale the number of rooms you can support. You still need a separate backend to know that a given room is hosted to a specific janus instance, so when a user wants to connect to a room, you point them to the right janus instance. Agones here would be useful to know on which janus instance you can create a room, or if you need to spawn a new janus instance, provisioning a new node on the k8s cluster eventually. |
I know you can get the number of sessions of the janus instance via the admin REST API already and it's indeed this metrics you want to use to know the load of a janus instance. And you also probably push some other janus metrics via an event handler plugin but I didn't look much on this side yet. |
Add prometheus instrumentation with crates prometheus and prometheus-static-metric to get details of the switchboard like number of rooms, users, sessions to be able to vizualize that with Grafana.
The
/metrics
endpoint can be added with tide / async_std (this is what janus-conference use) or axum / tokio (see also comments on #93)An agones Rust SDK integration may be interesting (or not I didn't dig this much yet) to scale horizontally janus instances on kubernetes. The Rust SDK is using tokio as a dependency already, and you get prometheus metrics too.
The text was updated successfully, but these errors were encountered: