Monitoring Bot Guide
Use the Webex monitoring bot for configuration lookups, execution history, and one-off runs.
What the bot can do #
- Return enabled monitoring configurations for a tenant.
- Show the latest execution attempt for each enabled configuration.
- Queue a one-off run for one configured building or network.
- Keep replies in the originating thread so busy Webex spaces remain readable.
Command pattern #
@Spaces <command> [tenant <tenant id|quoted tenant name>] [op <operation>] [name "<exact location name>"]
The current operation value is iot_infra for Cisco Spaces IoT infrastructure monitoring.
Common commands #
@Spaces active_configs
@Spaces active_configs tenant tenant-id-123
@Spaces active_configs tenant "Exact Tenant Name" op iot_infra
@Spaces last_executions
@Spaces last_executions tenant tenant-id-123
@Spaces last_executions tenant "Exact Tenant Name" op iot_infra
@Spaces run_location op iot_infra name "Building A - West"
@Spaces run_location tenant tenant-id-123 op iot_infra name "Campus Network 1"
@Spaces run_location tenant "Exact Tenant Name" op iot_infra name "Building A - West"
Tenant and location rules #
- Include
tenantin a multi-tenant room. The tenant must already be associated with the room through monitoring notification configuration. - Tenant IDs may be unquoted; tenant names containing spaces must be quoted.
run_locationonly works for configured building or network locations.- The
namevalue must use single or double quotes and is matched exactly; partial names are rejected.
What replies look like #
active_configsreturns a compact table with operation, location, last run, and last alert.last_executionsreturns the latest attempt for each enabled configuration, including notification and API-error state.run_locationsends an immediate validation reply, then posts the execution result in the same thread.- Command replies mention the requesting user so mention-only room notifications still work.