This feature requires having the Admin quality dashboard access privilege . If you don't have this privilege, ask your IT administrator.
Diagnose and troubleshoot meeting issues with the Meet Quality Tool (MQT). Admins or users with the Admin quality dashboard access privilegecan use the MQT to:
- Sort and filter meeting data
- Look at specific meeting stats
- See a timeline of events
- Learn more about live streams that use Google Meet’s Enterprise Content Delivery Network (eCDN)
The MQT is a tool for fixing problems, not for seeing data in real-time. This means some of the information might be delayed.
The MQT lets you see data including:
- Network statistics (jitter, packet loss, and congestion)
- Network connection delay (RTT)
- Microphone level and received audio level
- System (CPU) statistics
The MQT saves data for 30 days. For more information, go to Data retention and lag times .
Open the Meet Quality Tool
To access the MQT, you must be signed in to an account that has the Admin quality dashboard accessprivilege.
Access the tool from the Google Admin console
- Sign in with an administrator account to the Google Admin console.
If you aren’t using an administrator account, you can’t access the Admin console.
- Go to Menu Apps > Google Workspace > Google Meet .
Requires having the Service Settings administrator privilege .
- Click Meet quality tool.
- (Optional) If you're already logged in, you can search for a meeting code, organizer or participant by searching from any admin page.
Give users access to the MQT
Super administrators can give users access to the MQT. To do this:
- Create a custom admin role that has the Admin quality dashboard accesspermission.
- Assign the role to users.
Users with that role can only access the tool with the direct link. They can't access it through the Admin console.
For more details about admin roles and granting access, go to:
Filter & sort meeting data with the MQT
Expand section | Collapse all & go to top
Views
|
Meetings view |
Shows the meetings organized or joined by users in your organization. |
|
Participants view |
Shows the users in your organization that joined meetings. |
|
Google meeting room hardware |
Shows the Google meeting room hardware in your organization that joined a meeting. |
|
Suggestions |
Shows any suggestions available for your organization. |
Filter and sort
You can filter and sort the data to find:
- A meeting
- Data for one meeting room over a period of time
- Data for a specific real world location
- Problematic meetings or devices
- Meetings that happened on a specific day
- Meetings joined by more than 50 participants
- Live stream viewers don't count as participants
To filter data:
- Click Add a filter.
- From the list, select a filter.
- Set the filter values and click Apply.
- (Optional) To sort the filtered data, click a column header.
Summary bar
The summary bar shows info for the view you select.
Meeting, participant, & device statistics
| Statistic | Description |
|---|---|
| Meeting code | The meeting's joining code. |
| Starting time | Time the meeting started. |
| Duration | Average meeting time. |
| Location | Location of meetings. |
| Network congestion | Percentage of time that network issues kept a device from sending higher-quality video. |
| Packet loss | Percentage of packets lost on the network. This includes packets sent from a client to Google and received by the client from Google. |
| Jitter | Variation in latency on packets flowing between a client and Google. |
| Feedback score | User rating submitted at the end of a meeting. |
To review statistics about an event:
- On the left, click Meetings view .
- From the list, click a meeting to view detailed meeting information including a timeline of events.
Meeting summary
Information about the meeting. This includes:
- Meeting code
- Date
- Status
- Start and end times
- Duration
- Recording status
- Live stream views
- Organizer’s email
- Average feedback rating from participants
Live stream views are counted anytime someone joins the meeting to watch. If a single user joins and leaves multiple times, they count as multiple views.
When people connect from 3rd-party devices (interop gateways), their screen sharing feeds look like regular video feeds to other participants.
Meeting participants
List of meeting participants. For meetings in progress, details are updated as they become available.
For large meetings, you can add a filter to locate specific participants.
Each telephone endpoint for the same phone number is listed as a separate participant.
To see more details, click a participant's name. The Meet Quality Tool captures the following info:
- The participant's actions, such as turning the microphone or camera off or on.
- Screen sharing details, including the length of time the participant shared their screen.
- Network protocol changes (UDP, TCP).
- The network connection type (wired, Wi-Fi, cellular connections).
- If the participant was admitted after knocking, who admitted them.
- If the participant was ejected from the meeting, who ejected them.
- Audio and video transmission details.
- Screen sharing transmission details.
Meeting timeline
Timeline that visualizes how the meeting developed over time.
You can sort participants by name or join time. Hover your mouse over the icons to view more info.
The Participants section shows:
- When participants joined and all of the devices they used.
- If a participant joins with multiple devices, you'll see more than one device.
- Muteand unmuteactions
Click an endpoint icon to see a more detailed timeline of a single participant's activities and the system events that happened during a meeting. Use these to visualize the meeting quality as experienced by a user, which could help with troubleshooting.
Activities
The activities section shows start and stop times for:
- Screen sharing
- Recording
- Live streaming
Technical statistics
Learn about meeting details statistics
Shows if a participant joined from:
- Meet hardware
- Phone
- Phone used for audio with a video stream
- Computer
- Android
- iOS
- Interop gateway
- Unknown device
- Amount of audio or video information received or sent, in bits per second (bps)
- Available bitrate over time
- Actual bitrate over time
You can see Meet eCDN data for your meeting streams. If a meeting is recurring, each session has its own data. Data is always grouped by network name and retained according to the Workspace data retention policy . The available metrics are:
- Enablement rate: The percentage of viewers who are eligible to join a P2P network based on your organization's Meet eCDN settings. If your organization uses the Custom rules policy, this includes both allowed and blocked viewers.
- Savings rate: The percentage of traffic that viewers get from peers instead of the original media server.
- Media fallback rate: The percentage of viewers that go back to the original media server because P2P media quality or availability isn't good enough.
Admins can also get more data from APIs. For details, go to Google Meet Audit Activity Events .
Analyzing Silent Test results
When you turn on Silent Test mode for Meet eCDN , data generated by viewers will show up in the MQT as well. To easily distinguish between regular viewers and Silent Test viewers, the latter will have their network name prefixed by a “[Silent Test]” tag.
Get suggestions for your organization's Meet settings
The MQT analyzes meeting data to troubleshoot configuration issues. You can check the suggestions view to review instructions on how to solve the problem. Monitored issues include:
Expand section | Collapse all & go to top
Pre-requisites: Applies only to organizations using Meet eCDN .
Issue: A high media fallback rate in your organization’s Meet live streams means many viewers can’t receive P2P media, despite the peering policy . These viewers revert to the original media server, which reduces bandwidth savings.
Recommended action: Use the MQT eCDN table to identify networks with high fallback. If your organization uses the Custom rules policy, you can modify your rules to block the problematic networks, or further subdivide them into blocked and allowed ranges. If your organization uses a different policy, you can prepare a CSV and switch to the Custom rules policy for better P2P network oversight.
Pre-requisites: Applies only to organizations using Meet eCDN .
Issue: A low enablement rate in your organization’s Meet live streams means that many viewers don’t have Meet eCDN turned on. Ensure that your organization turns on Meet eCDN for viewers to maximize bandwidth usage efficiency.
Recommended action: Review Meet eCDN settings and expand enablement to include more user groups. Note that specific configuration groups or organizational units may have overriding settings. If you deliberately exclude large parts of your organization from Meet eCDN, you can ignore this recommendation.
Pre-requisites: Applies only to organizations using Meet eCDN with the Custom rules peering policy .
Issue: Your organization uses the Custom rules peering policy, but the rules don't match the IP addresses that your organization's live stream viewers use. As a result, viewers use the fallback peering policy instead. This means either that you haven't uploaded any rules, or that your rules don't account for all of the IP ranges that your organization uses.
Recommended action: Follow these steps to prepare a CSV file with custom rules, then upload it in the Meet eCDN settings. Or, you can select a different peering policy that requires less configuration, such as Subnet.
Pre-requisites: Applies only to organizations using Meet eCDN .
Issue: If your organization uses the Testing peering policy , it will cause viewers to randomly select their peers. This can result in poor media quality and an increase in bandwidth usage.
Recommended action: Select another peering policy for your organization. You can either prepare a CSV file and configure the Custom rules policy, or select the Subnet policy, which requires less configuration. Another option is to turn off Meet eCDN. If you’re deliberately collecting test data from live events , you can ignore this recommendation.
