WaSense Controller
API Explorer Docs Admin Login
WaSense Documentation

Daily Monitoring Summary Guide

Read the daily tenant monitoring digest and follow its signals into the portal.

On this page

Example message # 

example.com Daily Monitoring Summary
Mar 31, 2026

active monitoring configs: 1
runs attempted: 47
runs successful: 47
runs failed: 0
runs with API errors: 0
alerts sent: 0
suppressed unchanged: 0
APs observed: 143 (+0 vs previous day)
intent-tracked APs missing: 0
new APs in buildings with published intent: 0
buildings with alerts: 1
buildings with failures: 0
floors in maintenance mode: 0
portal: View execution history

How to use the summary #

  1. Check whether the run volume looks complete for the day.
  2. Look for failures, API errors, or alerting activity.
  3. Open execution history for the same date window when a number needs follow-up.
  4. Open the affected run to inspect tracebacks, alert delivery, and flagged issues.

Field reference #

Daily monitoring summary fields
Field Meaning Healthy signal Needs follow-up Where to look next
active monitoring configs Enabled configurations for the tenant during the day. Stable and matches intended scope. Unexpectedly low, high, or zero. Validate that the intended buildings and networks have monitoring enabled.
runs attempted Monitoring runs started in the day window. Matches enabled configurations and schedule cadence. A sudden drop or spike. Review execution history for the digest date range; low counts usually mean runs were not scheduled or created.
runs successful Runs not ending in an execution error. Close to or equal to attempted. Noticeably below attempted. Scan execution-history Status values and open error runs.
runs failed Runs ending in the error state. Zero. Anything above zero. Open failed runs, review Captured Tracebacks first, then Connector Overview for upstream collection failures.
runs with API errors Runs capturing one or more API tracebacks, even if the run completed successfully. Zero. Anything above zero. Scan API Errors in execution history and review api.* entries in Captured Tracebacks.
alerts sent Runs that delivered a Webex alert. Often zero on healthy days. Unexpected volume or delivery mismatch. Open runs with a triggered Alert and inspect Alert Delivery.
suppressed unchanged Alerts suppressed because state had not changed since the last successful alert. Can be normal during a persistent unchanged issue. Unexpectedly high or long-lived. Inspect Alert Delivery for the suppression reason and baseline execution.
APs observed Latest successful AP inventory per configuration and its daily delta. Stable day to day. Large unexplained changes or a missing expected baseline. Compare Current Totals and Connector Overview across recent successful runs.
intent-tracked APs missing Published-intent APs absent from the authoritative observed EDM AP inventory. Zero. Any unexplained non-zero value. Open execution detail and review inventory reconciliation for missing published AP rows.
new APs in buildings with published intent Observed APs without a row in the building's current published revision. Zero or an understood inventory change. An unexpected new AP count. Review inventory reconciliation and decide whether the deployment intent needs a new draft and publication.
buildings with alerts Building scopes with an alert-triggering run. Zero on quiet days. Any unexpected non-zero value or sudden increase. Use Alert Visualization for context, then inspect Flagged Issues in triggered runs.
buildings with failures Building scopes with a failed run or a run containing API errors. Zero. Anything above zero. Filter execution history to the building and review both Status and API Errors.
floors in maintenance mode Floors with active alert suppression at digest time. Zero unless planned maintenance is active. Unexpected or expired maintenance. Review the digest maintenance section and the floor suppression badge and expiry in Flagged Issues.

Portal workflow #

Start in execution history with the digest date range. Review Status, Alert, Notification, and API Errors. Open run detail for Current Totals, Connector Overview, Alert Delivery, Flagged Issues, and Captured Tracebacks. Use Alert Visualization for timing and multi-building patterns.

Quick triage rules #

  • Zero failures and zero API errors usually means collection ran cleanly.
  • API errors without failed runs usually indicate partial upstream degradation.
  • Alerts sent above zero means at least one threshold-crossing run should be reviewed.
  • AP inventory drops can hide other issues and deserve attention.
  • Maintenance mode suppresses alerting, not data collection.