-->

There are three types of log files automatically produced by the client that can be leveraged to assist in troubleshooting Microsoft Teams.

Open Finder → Applications → Utilities.; Double-click the Console item.; In the left part of the Console window, select system.log in the Files section.; On the Menu Bar in the upper part of the screen, click File → Save a Copy As.; In the dialog box that opens next, specify the filename, tags, and the location where the file will be saved. Jul 17, 2019  This issue is now resolved for all platforms in the following updates: KB4501375 LCU for Windows 10, version 1903.; KB4501371 LCU for Windows 10, version 1809 and Windows Server 2019.; KB4503288 LCU for Windows 10, version 1803.; KB4503281 LCU for Windows 10, version 1709.; KB4503289 LCU for Windows 10, version 1703.; KB4503294 LCU for Windows 10, version 1607. Mar 11, 2020  Crescendo is a real time event viewer for macOS that uses the ESF to show process executions and forks, file events, share mounting events, kernel extension loads, and IPC event data. ESF provides a vast amount of data, but the goal was to just pick.

• Debug logs

• Media logs

• Desktop logs

When creating a support request with Microsoft Support, the support engineer will require the debug logs. Having these logs on hand before creating the support request will allow Microsoft to quickly start troubleshooting the problem. Media or desktop logs are only required if requested by Microsoft.

The following table outlines the various clients, and their associated logs. Log files are stored in locations specific to the client and operating system.

For a complete list of supported operating systems and browsers, see Get clients for Microsoft Teams.

Debug logs

These are the most common logs and are required for all Microsoft support cases. Debug logs are produced by the Windows and Mac desktop clients, as well as browser based clients. The logs are text based and are read from the bottom up. They can be read using any text based editor and new logs are created when logging into the client.

Debug logs show the following data flows:

• Login

• Connection requests to middle tier services

• Call/conversation

The debug logs are produced using the following OS specific methods:

• Windows:

  Keyboard shortcut: Ctrl + Alt + Shift + 1

• Mac OSX:

  Keyboard shortcut: Option + Command + Shift+1

• Linux:

  Keyboard shortcut: Ctrl + Alt + Shift + 1

The debug logs are automatically downloaded to the following folders.

• Windows: %userprofile%Downloads

• Mac OSX: Downloads

• Linux: ~/Downloads

• Browser: You will be prompted to save the debug log to default save location

Media Logs

Media logs contain diagnostic data about audio, video and screen sharing. They are required for support cases only upon request and can only be inspected by Microsoft. The following table outlines the log location.

Desktop logs

Desktop logs, also known as bootstrapper logs, contains log data that occurs between the desktop client and the browser. Like media logs, these logs are only needed if requested by Microsoft. The logs are text based and can be read using any text based editor in a top down format.

Windows:

1. Right-click the Microsoft Teams icon in your system tray, select Get Logs

Mac OsX:

1. Choosing Get Logs from the Help pull-down menu

Linux:

1. Click on the Microsoft Teams icon in your system tray, select Get Logs

Event Viewer For Macos Mac

Event Viewer Mac Os

Related topics