Hello, I Wonder if there are any way to access to statistics of the instance (very global stats).
Thanks,
Hi and welcome. What statistics do you have in mind, can you give more details?
Hello,
I suppose you are asking about meet.jit.si?
I’m talking about instances that can be set up on our servers
For statistics we are currently using several options that you can configure it yourself: callstats, google analytics and amplitude.
// Stats
//
// Whether to enable stats collection or not in the TraceablePeerConnection.
// This can be useful for debugging purposes (post-processing/analysis of
// the webrtc stats) as it is done in the jitsi-meet-torture bandwidth
// estimation tests.
// gatherStats: false,
// To enable sending statistics to callstats.io you must provide the
// Application ID and Secret.
// callStatsID: '',
// callStatsSecret: '',
// enables callstatsUsername to be reported as statsId and used
// by callstats as repoted remote id
// enableStatsID: false
// enables sending participants display name to callstats
// enableDisplayNameInStats: false
// If set to true, disable H.264 video codec by stripping it out of the
// SDP.
// disableH264: false,
// How long we're going to wait, before going back to P2P after the 3rd
// participant has left the conference (to filter out page reload).
// backToP2PDelay: 5
},
analytics: {
// The Google Analytics Tracking ID:
// googleAnalyticsTrackingId: 'your-tracking-id-UA-123456-1'
// The Amplitude APP Key:
// amplitudeAPPKey: '<APP_KEY>'
// Array of script URLs to load as lib-jitsi-meet "analytics handlers".
// scriptURLs: [
// "libs/analytics-ga.min.js", // google-analytics
// "https://example.com/my-custom-analytics.js"
There is also the option to implement custom statistics.
import { getLogger } from 'jitsi-meet-logger';
import browser from '../browser';
import Settings from '../settings/Settings';
const MAX_CACHE_SIZE = 100;
// eslist-disable-line no-undef
const logger = getLogger(__filename);
/**
* This class provides an API to lib-jitsi-meet and its users for sending
* analytics events. It serves as a bridge to different backend implementations
* ("analytics handlers") and a cache for events attempted to be sent before
* the analytics handlers were enabled.
*
* The API is designed to be an easy replacement for the previous version of
* this adapter, and is meant to be extended with more convenience methods.
*
*
* The API calls are translated to objects with the following structure, which
* are then passed to the sendEvent(event) function of the underlying handlers:
Other than that different componenst has REST API with some statistics which you can query periodically and push to your choice of backend…
@damencho can you please comment if this has changed much since your comment in Nov '19 ? Thanks in advance.
Other than dropping the google analytics nothing has changed. Callstats and amplitude or implement your own analytics.
1 Like
Thank you!
I had searched, the amount of information makes it harder even though I read almost everything lately.
It would help if I could tag information and improve titles, please let me know if it’s possible to have such permissions here at some point.