| title | author | ms.author | manager | ms.reviewer | ms.date | audience | ms.topic | ms.service | ms.collection | search.appverid | description | appliesto | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Browser logs and tracing for Teams |
wlibebe |
wlibebe |
serdars |
xiashi |
10/10/2023 |
admin |
troubleshooting |
msteams |
|
MET150 |
Learn about Browser and WebRTC logs produced by Microsoft Teams, where they can be found, how to collect logs with Microsoft Support, and how they can help with monitoring and troubleshooting. |
|
For some categories of errors, Microsoft Support might require you to collect a browser trace. A browser trace can provide important details about the state of the Teams client when the error occurs. This article describes how to collect browser and WebRTC logs for Teams.
Before you start the browser trace, make sure that you’re signed in to Teams. It's important to sign in before you start the trace so the trace doesn't contain sensitive sign-in information.
After you’ve signed in, select one of the following links, as appropriate for your browser, and follow the provided steps.
Note
In the steps, replace all references to the Azure portal with the Teams client.
WebRTC logs can assist Microsoft Support by providing connection details for audio and video calls. Follow the steps to access the WebRTC logs in Microsoft Edge (Chromium) or Chrome:
-
Open a new tab and go to one of the following URLs:
- Microsoft Edge (Chromium):
edge://webrtc-internals/ - Chrome:
chrome://webrtc-internals/
- Microsoft Edge (Chromium):
-
Open the Teams Web application and reproduce the problem.
-
Go back to the tab that was accessed in step 1 and you'll see at least two tabs:
- GetUserMedia Requests
https://teams.microsoft.com/url
-
Choose the tab with the name of the Teams application and save the page content.
Configure log files for monitoring and troubleshooting in Teams