All WFO demos
DemoT-1002Monitoring alert

Trace an alert to the customer

The agent resolves a device and interface to a WFO subscription and customer, then checks maintenance flags against administrative and operational state.

Service mapping · live diagnostics See the setup
≈70 seconds · silent · English Edited waiting time · emulated lab

What the agent does

  • Resolve sites and interfaces to WFO subscriptions, UUIDs and customers.
  • Query specialist agents over A2A, using MCP tools for WFO, NetBox and network data.
  • Correlate stored configuration with device state and path measurements.

The exact request

Monitoring reports oper-state down on clab-orch-demo-par-p ethernet-1/2. Which service and customer use it? Is this expected maintenance or a fault, and what is the impact?

Multi-agent architecture

Hover, focus or tap a node to explore

One planner. Three specialists. Shared evidence.

A2A connects the agents; MCP exposes their tools. Network tools compare WFO intent over REST and GraphQL with SR Linux state over JSON-RPC. Select a node to follow its connections.

Validation and execution boundaries

The agent investigates and recommends; people decide and act. Each step keeps a finding tied to evidence and keeps any change under operator control.

  • Confirm the target. Check that the subscription UUID, customer and exact interface match the ticket, so the diagnosis is not about a neighbouring service.
  • Compare intent with evidence. WFO stores what should be configured; the device reports what is happening. A subscription that is active or in sync does not prove the link is healthy, so both sources are read.
  • Keep changes separate. The agent never restores a port or edits a maintenance flag in this demo. An operator reviews the diagnosis and approves any follow-up as its own step.

Questions about this demo

Is this a production incident?

No. These are example tickets in an emulated three-node network. Real SR Linux instances carry the lab traffic. Static tickets stand in for a ticket system; automatic ticket-system integration is not demonstrated.

Does the assistant make changes?

This demo is read-only. It reports findings and recommends next steps. An operator must authorize restoration or maintenance separately; no repair, port change or maintenance flag update occurs in the recording.

Is the recording real time?

The silent English recording is about 70 seconds long. Model waiting has been compressed; this is an edited demonstration, not a benchmark. The final comparison and recap combine recorded WFO intent with independently captured device evidence.

Explore the implementation

Explore the agent and example stack. The network specialist and containerlab extend the base agent setup shown in the documentation.