Speed Up OpenTok Session Debugging with Inspector

OpenTok Session Debugging with the Inspector tool

Diving into data on OpenTok sessions can provide developers with the tools they need to understand bugs and make improvements quickly. That’s why we built Inspector – a tool to help developers understand what happened in specific OpenTok sessions. Users can either enter a session ID or use the Session Dashboard to access the information. This includes user data, errors, video and audio quality and events about a session.

Since first launching Inspector a few years ago, we’ve received feedback from users on some improvements they would like to see in order to make more informed decisions on sessions and debug more efficiently. So we’ve been working on these improvements over the past few months. Today, we’re excited to make them available to all users.

Have a better understanding of your users

One of the first areas we wanted to focus on was user insights. We recognized the need to provide developers with more data on who their end users are. This would let developers match the user IDs in Inspector to the real-life participant who experienced issues. So we’ve added end user data to the Inspector dashboard, including location, device and time connected. This allows developers to get an at-a-glance overview of their users and more quickly understand and identify problems.

OpenTok Session debugging filters for User data

We’ve also provided an additional layer of user data to give developers insights around connection IDs, subscribers, publishers, and end reason, in order to quickly identify issues within the session.

OpenTok Session Debugging User data view

Get a high level view of session errors

We’re also now providing developers with a high-level view of errors across sessions before diving into events or quality data. This saves valuable time in the OpenTok session debugging process.

OpenTok Inspector Error log view

If any errors occurred in the session, they will display in the Error Log section. This section also displays the failure rate for connection, publish, and subscribe attempts in the session or meeting. This rate is calculated by dividing the number of failures by the total number of attempts.

Filter data and quickly drill down on what matters

Finally, we wanted to make it easier for our developers to drill down and filter data across data types. This lets them focus more quickly focus on what matters, saving hours of time. We especially recognized the need for this feature as we were continuing to add more data to Inspector, and we needed to give users an easy way to filter this data.

inspector tool for OpenTok session debugging Meeting statistics view

Now, developers can filter data by users, allowing developers to easily identify users and filter them from anywhere in the app. We’ve also made improvements to the user navigation. This lets developers easily navigate between different sections of Inspector, including Summary, Errors, Quality Metrics and Events.

With these improvements, we aim to provide a more efficient experience for developers and allow them to pinpoint session-related data more quickly. This will make OpenTok session debugging a much easier process. We welcome developer feedback on these updates, as well as other additions you would like to see in Inspector, or any of our other developer tools