Autosaving meeting QoS statistics

As an admin, you can use the Network Connectivity Tool to generate a local client log file for advanced meeting Quality of Service (QoS) statistics when troubleshooting issues. This feature is useful when needing detailed insights into network performance during real-time communications and for organizations requiring deeper analysis to generate sensor data for troubleshooting.

Note: Ingesting and reporting on these logs is a manual process. Zoom does not provide support for log ingestion or reporting.

Prerequisites for using the Autosave QoS Stats feature

• Zoom desktop app for Windows or macOS: Global minimum version or higher
• Administrative permissions if using policy controls such as GPO, MSI, or PLIST

How to enable Autosave QoS Stats

Manually enable Autosave QoS Stats for individual users

Individual users who are not part of an organization or a policy controlled account can manually activate Autosave QoS Stats.

1. Access the Network Connectivity Tool.
2. In the top-right corner, click the setting icon .
3. Select the Autosave QoS Stats check box.

Enable Autosave QoS Stats for multiple users and configure using policy controls

You can enable and configure Autosave QoS Stats by utilizing GPO, MSI, or PLIST policies as described in the Mass Deployment guide then add the following:

• EnableDiagnostic: Controls the Network Connectivity Tool.
• EnableDumpTPstatInfo: Controls Autosave QoS Stats.

Enable Autosave QoS Stats for multiple users using a command line

You can enable or disable Autosave QoS using a command line:

• Windows: Enter C:\Program Files\Zoom\bin>Zoom.exe --qlog=on or Zoom.exe --qlog=off
• macOS: From terminal, enter open zoomus://--qlog=on or open zoomus://--qlog=off

Note: Quality of Service telemetry logging will begin immediately for all active and future meetings once enabled.

How to locate Autosave QoS logs

Autosave QoS logs for each meeting are saved in the tpstat folder with the format tp_stat_<meeting number>_<index>.log (e.g. tp_stat_12345678915_0.log). Each meeting can have up to two log files with a maximum size of 50 MB each. When the limit is reached, the oldest files are automatically overwritten by the most recent logs, ensuring only the latest four logs will be present in this directory at any time.

• Windows file path: C:\Users\%user%\AppData\Roaming\Zoom\logs\tpstat
• macOS file path: /Library/Logs/zoom.us/tpstat

How to interpret log files

Log file data

The log files include these Quality of Service details:

• Audio: Latency, Jitter, Packet Loss
• Video: Latency, Jitter, Packet Loss, Resolution, Frame Rate, Mean Opinion Score
• Share: Latency, Jitter, Packet Loss, Resolution, Frame Rate, Mean Opinion Score
• WiFi: RSSI

Log file format

Each line of the log file is valid JSON data and can be formatted as follows:

{
 "audio": {
  "recvInfo": {
   "avgLoss": "0%",
   "jitter": "4ms",
   "latency": "7ms",
   "maxLoss": "0%"
  },
  "sendInfo": {
   "avgLoss": "0%",
   "jitter": "4ms",
   "latency": "7ms",
   "maxLoss": "0%"
  }
 },
 "share": {
  "recvInfo": {
   "avgLoss": "0%",
   "fps": "19fps",
   "jitter": "4ms",
   "latency": "7ms",
   "maxLoss": "0%",
   "res": "1920*1080"
  },
  "sendInfo": {
   "avgLoss": "N/A",
   "fps": "N/A",
   "jitter": "N/A",
   "latency": "N/A",
   "maxLoss": "N/A",
   "res": "N/A"
  }
 },
 "timeStamp": 1717654324777,
 "video": {
  "recvInfo": {
   "avgLoss": "0%",
   "fps": "12fps",
   "jitter": "4ms",
   "latency": "9ms",
   "maxLoss": "0%",
   "res": "256*144"
  },
  "sendInfo": {
   "avgLoss": "0%",
   "fps": "27fps",
   "jitter": "2ms",
   "latency": "10ms",
   "maxLoss": "0%",
   "res": "640*360"
  }
 },