Mqttable
Back to docs

PCAP analysis detail: packet diagnosis you can cite

How one analysis keeps packet rows, checks, issue groups, root-cause candidates, and handoff links together.

Jun 24, 2026Mqttable EngineeringMqttable Engineering

/pcap-analysis/:analysis_id 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

Packet grid beside checks, issue groups, root-cause candidates, and replay handoff.

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

placeholder

Human job

  • Inspect packet rows, protocol fields, findings, and diagnostic check details.
  • Open root-cause candidates without losing packet context.
  • Create Replay handoff only when the capture supports a useful scenario.

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.