Cross-Domain Orchestrator
Custom agent·policy router + tools
Connected
T1 · InlineFull fidelity·The agent's model and tool calls route through Sentry's gateway.
Full conversations this agent has run – every model message and tool call captured in order through the Sentry gateway, with the input and output tokens billed at each step.
Correlate the Auckland fibre cut across domains
Today, 09:05 · 6 steps
↘ 7,502 in · ↗ 5,756 out
Engineer
We have a fibre cut alarm in Auckland. What's the blast radius across the network and which customers are impacted?
↘ in 52↗ out 0
OrchestratorI'll correlate the transport alarm with core routing and then resolve impacted services from OSS/BSS.
↘ in 980↗ out 96
Tool callNokia NSP
→ requestGET /alarms?region=AKL&severity=critical
← responseSpan AKL-CBD-03 down (LOS); protection path congested at 92%
↘ in 110↗ out 1,400
Tool callEricsson NMS
→ requestGET /routes/affected?span=AKL-CBD-03
← response2 P-routers rerouted; 1 BGP session flapping (AS64512)
↘ in 120↗ out 1,700
Tool callNetcracker
→ requestGET /services/impacted?span=AKL-CBD-03
← response1,284 services degraded · 37 enterprise SLAs at risk · 3 priority customers
↘ in 140↗ out 2,200
OrchestratorRoot cause: fibre cut on span AKL-CBD-03 (LOS), protection path now at 92% congestion. 1,284 services degraded, 37 enterprise SLAs at risk, 3 priority customers. Recommend traffic-engineering an alternate path and pre-emptive SLA comms. Want me to open the incident?
↘ in 6,100↗ out 360
Why is customer Meridian double-billed?
Yesterday, 11:48 · 4 steps
↘ 5,455 in · ↗ 4,000 out
Engineer
Meridian says they were billed twice this cycle. Can you trace it?
↘ in 30↗ out 0
Tool callNetcracker
→ requestGET /billing/Meridian?cycle=current
← response2 active subscriptions for same circuit ID CIR-9920
↘ in 95↗ out 1,600
Tool callSAP
→ requestGET /assets?circuit=CIR-9920
← responseCircuit migrated 2023; old asset record never deprovisioned
↘ in 130↗ out 2,100
OrchestratorThe double-bill comes from a stale ERP asset record: circuit CIR-9920 was migrated in 2023 but the old subscription was never deprovisioned, so OSS bills both. Fix: retire the legacy asset and credit one cycle. Flagging to Finance.
↘ in 5,200↗ out 300