Monitoring Benefit
The Hourly view of the Simplified Teams Call Quality Dashboard is the one to use while something is happening. It reports the same reliability and quality metrics as the Daily and Monthly views, but broken down by hour and with an hour-over-hour percentage change.
That change figure is what makes this view useful during an incident. A tenant can sit at a packet loss rate that looks unremarkable as a daily average while a specific hour is badly degraded, and the daily figure will not tell you when it started. The hourly view will.
The three periods answer different questions:
- Hourly — this page. Is something wrong right now, and when did it start?
- Daily — is today worse than normal?
- Monthly — is call quality getting better or worse over time?
The page can be opened directly on the ENow web server:
http://localhost:20080/MailscapeWeb/MicrosoftTeamsCQDHourly.aspx?server=Office-365
Replace localhost with the web server's host name if browsing from elsewhere, and 20080 with your own port if it was changed at installation.
What is measured
The metric set is the same across all three periods and is documented in full on the Daily page:
- Reliability — Total Call Setup Failure Percentage, Setup Failure Rate Percentage, Total Drop Call Percentage
- Quality — Audio and Video Poor Stream Counts, Average Round Trip, Average Packet Loss Rate, Average Jitter
- Rate My Call — users' own ratings, including a Tier 1 executive list
What is specific to this view is the hour-over-hour percentage change shown against the metrics, which is what turns a static number into a direction of travel.
Reading the hourly view during an incident
Three patterns are worth recognising:
- Degradation that tracks the working day — climbing through the morning, peaking mid-afternoon, clearing overnight. That is contention. The link or the path is sized for less than it is carrying.
- Degradation that starts abruptly and stays flat — a change rather than a load problem. Something was reconfigured, failed over, or started routing differently. Note the hour and compare it against your change record.
- Degradation confined to one or two hours, then clear — usually a transient event upstream. Worth noting, not worth chasing unless it recurs at the same time each day, which points at a scheduled job competing for bandwidth.
Three different kinds of "nothing here"
This view is the easiest of the three to misread, because an empty bucket is often correct. Separate these before investigating anything:
| What you see | What it means |
|---|---|
| The most recent hour or two are empty | Normal. Microsoft's call quality data arrives with a delay. Read the most recent hours that have data instead. |
| An out-of-hours bucket is empty or shows an extreme percentage | Normal. Few or no calls were placed. Check the call volume behind the figure before treating it as a finding. |
| The page reports that no test results have been received, across every hour | Collection has not run. This is not a call quality fault and no threshold has been evaluated — nothing arrived to evaluate. Work it as a collection problem. |
That last case is the one worth recognising on sight: "no results received" and "test failed" look alike on a dashboard and mean opposite things. One says call quality breached a threshold; the other says call quality was never measured. Work the collection checks in Microsoft Teams - VIP Monitoring Status rather than investigating the network.
Where the thresholds are set
Warning and critical thresholds are configured in the Office 365 thresholds section of the ENow Admin Console, and are per-install. Confirm the values in force in your own console before treating an indicator as unexpected.
How do we verify the monitoring test results?
- Allow for Microsoft's reporting delay. This matters more on the hourly view than anywhere else. Call quality data is not real time and can take hours to arrive, so the most recent hours will look empty or incomplete even during an active problem. An empty current hour is normal, not a fault.
- Compare against Microsoft's Call Quality Dashboard at cqd.teams.microsoft.com for the same hours.
- Watch the call volume per hour. Hourly buckets contain far fewer calls than daily ones, so percentages swing much harder. An out-of-hours hour with three calls in it can show an alarming figure that means nothing.
Common warning or error results, and potential solutions
| Result | Potential solution |
|---|---|
| The current hour is empty | Expected. Microsoft's data arrives with a delay — check the most recent hours that have data rather than the newest bucket. |
| Wild swings on overnight or weekend hours | Low call volume. Check the number of calls behind the percentage before treating it as a finding. |
| A sharp rise at a specific hour | Note the hour and check it against change control, circuit failovers and any scheduled bulk transfers. |
| A daily pattern that peaks every afternoon | Contention rather than a fault. This is a capacity conversation — use the Monthly view to show whether it is worsening. |
| Alerts firing repeatedly on brief hourly spikes | The hourly view is more sensitive by nature. If short spikes are not actionable in your environment, tune the thresholds for this check rather than disabling it. |
| The page reports that no test results have been received | Not a call quality fault. Collection has not run — see the section above, and the data collection checks in Microsoft Teams - VIP Monitoring Status. The Teams views share a collection pipeline and normally fail together. |
Comments
0 comments
Article is closed for comments.