Rest API endpoint /colibri/conferences missing in release 2.0.8044 on videobridge?

21

These are quite different, and I’m not sure which ones you want at globally vs at the conference level. Let’s look at them one-by-one:

conference ID: A list of conference IDs used to be available in /colibri/conferences, it is currently available under /debug

jvb ID: You could get this elsewhere, or you can use relay-id from /colibri/stats

region: Available in /colibri/stats

number of participants: We have the global in /colibri/stats and /metrics. For the conference level you can get it from /debug. I think you used to be able to get it by analizing the /colibri/conferences output, but not directly.

duration: this was never available from /colibri/conferences, but you should be able to get it from /debug (as creationTime)

bitrate and bytes transferred: /colibri/stats has the globals. We don’t have them at the conference level, but you can get them at the endpoint level from /debug. This was never exposed in /colibri/conferences.

CPU and RAM: we don’t expose these, you should get them from the OS. We do have stress_level though.

1 Like
22

Thanks for the detailed reply @Boris_Grozev !

I’m going to study the different options in detail.

Thanks again

Edit: I have a question about the /debug endpoint. I’m using prometheus to scrape metrics but if I point the scraper at /debug I get an error because I’m assuming the data is not in prometheus format. Am I missing something obvious?

23

hello @damencho , http://localhost:8080/colibri/stats/ status will be okay.
http://localhost:8080/colibri/conferences not working for me what kind of issue is that ?

and why jitsi use colibri rest api? and can we implement swagger ?

Thank you in advance.

24