Mqttable
Back to docs

Monitor Events: runtime history you can investigate

How Mqttable records connection failures, publish notices, scheduled-message errors, and issue groups.

Jun 24, 2026Mqttable EngineeringMqttable Engineering

/monitor/events is a product surface in Mqttable. It exists because MQTT debugging needs a place for this job, not because every task should start from MCP. This page focuses on the product workflow. MCP support is a companion layer: use it when automation helps, not as the starting point for every task.

Interactive diagram

Runtime event stream to issue grouping to related trace or replay evidence.

Placeholder for the interactive diagram. Replace with the generated artifact when ready.

placeholder

Human job

  • Review errors and notices without scraping terminal logs.
  • Filter by severity, time, broker, client, or problem group.
  • Use events to explain why a publish, schedule, proxy, or replay behaved differently.

Automation handoff

  • MCP and CLI are supporting surfaces here, not the whole story.
  • Use MCP reads when the same state needs to be inspected by an agent.
  • If an action changes MQTT state, use schema, plan, confirmation, apply, and verify.

Boundary

Keep this surface focused. If the job belongs to another workflow, move there instead of turning one page into everything.