The number of different endpoints used in the meeting. Mouse over the SDKsĮntry to see a list of the different SDKs and the number of users for each. The number of different Vonage Video API SDKs used in the meeting. The number of issue occurances in the meeting. The total number of streamed minutes in the meeting. If there are SIP users connected to the meeting, The number of individual users, connections, published streams, and subscribers to the streams This can be multiparty, one-to-one, one-to-zero, or broadcast. The Meetings Statistics panel includes the following information: In cases where a session includes many distinct meetings, this can help simplify the view for easier debugging. In some cases, you may want to drill down to specific meetings within a larger session - to do this, simply click the Meeting Selector in the top right corner and select the meeting segment you’re interested in viewing. It’s also helpful for verifying that you’re looking at the correct session when debugging. This data can be helpful for developing a quick understanding of the session topology, length, and diversity. These sections provide a high-level overview of what happened in a session. Searching for SessionsĪt the top of the view are the Summary and Statistics sections. You must be logged into your Vonage Video API account to access Inspector, and you can only view sessions created from API Keys associated with your account. Inspector is primarily used for debugging problematic sessions that have occured in your OpenTok application. Users can either enter a session ID or use the Session Dashboard to access the following information about a session:
Inspector is a tool to help understand what happened in specific OpenTok sessions.
This page includes the following sections:įor information on data retention and latency. A post-call diagnostic tool for your Video API sessions
0 kommentar(er)
