This is just an example of how you can build an UI on top of
the existing Admin/Monitor interface. This page
will only work as it is if you enabled the API (which is
disabled by default) and you're using the default values. Edit
the backend settings in the admin.js JavaScript
code to adapt it to your configuration if you changed
anything.
The Server Info tab, as the name suggests,
provides you with a view of the information related to the
Janus instance you're using, e.g., in terms of the features
that have been enabled, the modules that are available and so
on. That's the same info you'd get contacting the Janus API at
the /janus/info backend.
The Settings tab instead allows you to inspect a
few of the current settings in Janus (e.g., debug level and so
on) and provides you with a way to change them dynamically.
The Plugins tab presents the list of media
plugins available in this Janus instance, and allows you to
interact with them, assuming they implement the
handle_admin_message API. The
Transports tab does the same for transport
plugins, and allows you to send requests to tweak the
behaviour of the plugin or query its internal state, assuming
they support this somehow.
The Handles tab allows you to browse the
currently active sessions and handles in Janus. Selecting a
specific handle will provide you with all the current info
related to it, including plugin it is attached to, any plugin
specific information that may be relevant, ICE/DTLS states,
amount of data being exchanged and so on. This section is
especially helpful when you want to debug issues with a
PeerConnection: you can find more details in
this blog post.
Finally, the Stored Tokens tab allows you to list
existing authentication tokens, create new ones, associate
plugin permissions and the like. This feature will only be
possible if you enabled the stored-token authentication
mechanism in Janus, of course.