WaSense Controller
API Explorer Docs Admin Login

Monitoring Configuration

Create reusable monitoring profiles, assign building configurations, and validate the first run.

On this page

Monitoring is independent #

A monitoring profile is a tenant-scoped reusable template for operational behavior. A monitoring configuration assigns one of those profiles to a building or building-equivalent network. Neither object requires IoT intent, an IoT deployment, or published AP intent.

Without IoT intent, monitoring still evaluates operational health and data quality and simply skips desired-configuration comparisons.

Create a monitoring profile #

  1. Open the tenant, then select Monitoring Configuration and Monitoring Profiles.
  2. Select New Profile and enter a profile name, default interval, and optional description.
  3. Set the floor-beacon and IOx app-channel age and floor-impact thresholds.
  4. Configure Webex destinations and alert behavior if notifications are required.
  5. Choose an authentication mode and complete its required settings.
  6. Save the profile. The same profile can be assigned to multiple locations.
Keep monitoring and intent separate

Monitoring profiles do not contain desired UUID, BLE mode, gateway mode, beacon profile, or IOx version. Define desired configuration in a separate IoT intent profile.

Profile settings #

Area Available settings
Settings Profile name, default interval, and optional description.
Thresholds Floor Beacon Stale Minutes, IOx App Channel Minutes, Floor Beacon Floor Impact %, and IOx App Channel Floor Impact %.
Webex Settings Enable alerts, alert mode, transition lookback, optional exclusion of unconfigured APs using IoT intent, token/default bot, destinations, detailed output, attachments, change-only delivery, and triggering-floor filtering.
Authentication Sys Token, App Bearer, API Bearer, or Hybrid routing.

Authentication choices #

Mode Use and requirements
Sys Token Uses a current sys-token supplied for a manual run. Scheduled execution must have an available credential path.
App Bearer Requires monitoring.use_spaces_dev_bearer and a regional Spaces developer key configured on the server.
API Bearer Uses a stored, externally generated bearer token.
Hybrid Routes EDM, DMS Proxy, and Status V2 independently between sys-token and app bearer.
Bearer bootstrap

A tenant bearer subject may first need to be bootstrapped by running with a sys-token. Manual runs prompt for a sys-token whenever the selected profile or hybrid route requires one.

Assign and enable monitoring #

  1. Select a building or building-equivalent network in the tenant hierarchy. Floor-scoped configurations are not supported.
  2. Open Monitoring Configuration and Location Configuration.
  3. For Spaces IoT Infra, select the required monitoring profile.
  4. Independently choose an intent profile if configuration-aware monitoring is wanted. Blank inherits the tenant default; when no default exists, no configuration intent is evaluated.
  5. Optionally override the interval, choose periodic API families, and limit connector names.
  6. Check Enabled and select Save.

The intent selector updates the same shared building assignment displayed in IoT Configuration; it is not a monitoring-only copy. There is at most one configuration for each tenant, location, and monitoring concept. If the UI preselects the only available monitoring profile, that profile is still required before saving or running.

Run the first validation #

  1. Supply a sys-token if the effective authentication mode requires one.
  2. Select Run Now and wait for the execution to finish.
  3. Review status, API errors, floor rollups, configuration and operational findings, and data-quality issues.
  4. Open Active Configs to confirm the configuration is enabled and has the intended cadence.
  5. Open Monitoring History and Execution History to confirm the first run and subsequent schedule.

Intent and remediation behavior #

Monitoring uses current published per-device intent first. Otherwise it uses the assigned live profile overlaid on the tenant default. Draft revisions do not affect monitoring. Profile fallback is always alert-only.

Automated remediation is possible only for published per-device intent when the deployment is active, has a current published revision, and its Allow automated remediation safety gate is enabled in IoT Configuration. Scheduled monitoring has no second location-level remediation toggle.

API-first behavior #

The dashboard is a client of the monitoring profiles, configurations, catalog, configuration-run, and audit APIs. IoT intent assignments use the same intent profile and assignment APIs as IoT Configuration; the dashboard does not maintain separate business rules or a second copy of intent.

Primary profile, assignment, and validation APIs
/api/v0/monitoring/spaces/profiles/
/api/v0/monitoring/spaces/configurations/
/api/v0/monitoring/spaces/configurations/catalog/
/api/v0/monitoring/spaces/configurations/{id}/run/
/api/v0/monitoring/spaces/audits/
/api/v0/spaces/iot/intent-profiles/
/api/v0/spaces/iot/intent-assignments/
/api/v0/spaces/iot/deployments/
/api/v0/spaces/iot/revisions/
/api/v0/spaces/iot/managed-aps/