Knowledge Documents 0 files
📄
High-Level Design
HLD document (PDF, DOCX)
📋
Low-Level Design
LLD document (PDF, DOCX)
📝
SOPs & Runbooks
Operational procedures
Network Data 0 files
🔢
Subnet & IP Plan
CSV, XLSX — subnet definitions
🗺️
Sites Data
Location, criticality, business function
Declared Tooling Stack From architect intent
Service edges · PE routers
Cisco IOS-XRNCS 5500 · 57xx · 14 PEs
Backbone transit · P routers · Peering
Juniper JunosPTX10008 P · MX10008 PEER
Route Reflectors (vendor-diverse)
Cisco IOS-XRRR1-LON1 Nokia SR OSRR2-FRA1 · 7750
Optical line systems
Ciena 6500LON-FRA InfineraAMS ADVAPAR-MAN
EMS · NMS · ITSM
🖥Cisco EPN Manager 🖥Juniper Paragon IBM Netcoollegacy · migrating 🎫ServiceNowCHG · INC · CMDB
All vendor APIs polled by LinkEye Collector (gNMI / NETCONF / SNMP). EMS data ingested for correlation. Any divergence between declared intent and observed reality becomes a drift finding.
Architect Intelligence Chat
AI-guided
LE
Welcome, Architect.
I'm here to help build the onboarding knowledge graph for your network. Let's start with intent — tell me about the network you've designed. What is it built to support, and what are the most critical sites or services?
Design Intent Knowledge Graph building…
0
Sites
0
Services
0
Subnets
0
Relations
Upload documents or chat to build graph
Site Service Business Function Critical Subnet
Polling Engine
Overall collection 0%
0
Devices
0
Sources
0
Metrics/s
0
Events
Active Collection Tasks
Live Topology Graph Building current state… 0 nodes
📡
Polling initializing…
Healthy Warning Critical External Source
Collection Evolution
Phase 1 — Discovery
SNMP/SSH sweep of all declared subnets. Device inventory established.
Phase 2 — Telemetry Expansion
gNMI streaming enabled on supported devices. NetFlow/IPFIX activated on edge routers.
Phase 3 — Controller Integration
Meraki, Cisco DNA Center APIs polled. Wireless client & AP data ingested.
Phase 4 — Extended Sources
APM, SIEM, DDI integrations activated based on discovered services.
External Integrations
Collection Insights
Awaiting data…
Context Sources14 integrated
🎫
ServiceNow
CHG · INC · CMDB · customer tickets
LIVE
CMDB CIs~3,800 backbone + customer
CHGs (24h)7 · 2 caused findings
Open INCs5 (F1 · F3 · F5 · F7 · MW)
☁️
LinkEye Data Collector
Unified ingest · multi-vendor
LIVE
Devices polled~30 (5 POPs)
ProtocolsgNMI · NETCONF · SNMP
Snapshot cadence30s state · 5min config
🌐
LinkEye BGP Monitor
BMP · BGP-LS observation
LIVE
eBGP sessions14 monitored
iBGP sessions~70 monitored
Drift detections (24h)2 · F1 + F3
👁
LinkEye Customer SLA Probe
CPE-side synthetic probes
LIVE
CPEs probed~2,400 customer VRFs
Probes / hr~144k
SLA-affected now1 · cust-12345 (F3)
📊
LinkEye IPFIX Aggregator
Flow telemetry · sampled 1/1000
LIVE
Ports monitoredpeering + customer-facing
Used by F6capacity forecast modeling
gNMI · Cisco IOS-XR
14 PEs + RR1-LON1 · streaming
LIVE
Devices15 · NCS 5500 + 57xx
Subscriptions~600 active
Data rate~12 MB/min
NETCONF · Juniper Junos
P-routers (PTX) + peering edges (MX)
LIVE
Devices8 · 5 PTX + 3 MX
Config changes (24h)3
TE tunnels tracked~140
Nokia SR OS · NETCONF
RR2-FRA1 · vendor-diverse
LIVE
iBGP clients8 (was 18 · F2)
BGP CPU12%
🖥
Cisco EPN Manager
EMS · IOS-XR estate
LIVE
Devices covered15 IOS-XR
Alarms (24h)1,847
Auto-suppressed1,802 · 97.6%
IBM Netcool (legacy)
NMS · being migrated to LinkEye
LIVE
Raw alarms (24h)~4,247
After correlation8 findings · 99.8% reduction
Ciena 6500 Optical EMS
LON-FRA long-haul
LIVE
Channels monitored88
Pre-FEC trending1 · channel 41 · F4
🔭
External BGP Looking Glass
route-views + 4 public LGs
LIVE
Used by F1prefix-leak external verification
🔐
RPKI Validator (Routinator)
ROA + ASPA validation
LIVE
ROAs ingested~480k
Invalid blocked (24h)~80
PTP / SyncE Monitor
Time-sync telemetry
LIVE
Grandmasters2 · LON1 + FRA1
Slave nodes42 across backbone
GM failovers (24h)3 · F5 finding
Operational Knowledge Graph 0 nodes
🔗
Loading operational context…
Site / NOC Device (13 managed) Service / DEX / Tool Finding · CHG · INC Architect (intent owner)
Recent IncidentsServiceNow · 24h
CHG-2026-5510
Peer-export policy edit on PEER-LON1 · caused F1 prefix leak
May 19 · 06:18 UTC · CAB-approved · closed successful (but caused F1)
NT-2026-5511
External peer NOC ticket · "341k+ prefixes from your AS" · matches F1
P1 · raised by peer 10:40 UTC · 4h22m after CHG
TX-2026-9914
cust-12345 · branch-MAN cannot reach HQ subnet · matches F3
P1 · SLA clock running · 13min remaining
TX-2026-9920
cust-22810 · intermittent host service · matches F7 EVPN MAC mobility
P2 · customer-side L2 loop confirmed
TX-2026-9911
MNO customer · carrier-aggregation drops on 4 LON cells · matches F5
P2 · GPS jamming external cause
M-2026-0520-A
Maintenance window · PAR1 line-card swap · 487 alarms suppressed
In-progress · expected end 14:00 UTC
Team & Ownership
NOC
NOC · 24×7
primary + DR site · follow-the-sun rotation
ONCALL
ARC
Network Architect
HLD / LLD owner · peering policy + RR design + optical thresholds
CAB
Change Advisory Board
7 CHGs reviewed (24h) · 1 leak post-mortem pending
Operational Memorylearned patterns
Active findings by domain
Peer-policy drift detection F1
RR cluster balance · IGP-driven F2
L3VPN VRF RT validation F3
Pre-FEC BER trending (optical) F4
PTP sync drift · backhaul F5
Peering capacity forecast F6
8 active findings across 6 operational domains. Alarm Correlator absorbed 4,247 raw alarms into these 8 actionable items (99.8% reduction).
L01 · Design Intent Graph · 24 nodes L02 · Telemetry Graph · 16 nodes L03 · Onboarding Intelligence · 16 nodes TESSERACT · 0 SEMANTIC ENTITIES 0 semantic edges
One entity · eight dimensions · everything connected
The three lower-layer graphs (declared intent, live telemetry, operational state) are fused into a single semantic model. Each entity — a device, site, service, person — is viewable across 8 dimensions simultaneously. Click any node to see what it was designed to be, what it's doing right now, who owns it, what depends on it, and what's gone wrong before — all in one view. This is what makes agentic reasoning possible.
⌘K
P1-LON1 · backbone P cust-12345 L3VPN LON1 POP NOC L3 Backbone role F1 · prefix-leak pattern eBGP / iBGP control plane
Semantic Dimensions 8
Tesseract Graph Overall view · all dimensions fused 0 entities
Initializing semantic fusion across Design Intent, Telemetry, and Onboarding Intelligence graphs…
Device Site Service Person/Team Business Fn Click any node to explore across 8 dimensions
Entity — Tesseract View select entity
Search or click any entity in the graph to view it across all 8 semantic dimensions — Design, Telemetry, Operational, Protocol, Dependency, Risk, History, and Business meaning.
0
Requests / min
6
Active Consumers
14
Tools Exposed
42ms
p50 Latency
MCP Tools Exposed 14
MCP Gateway — Live Traffic Semantic Tesseract → Consumers
Live Request Log
0 req/s
Active Consumers 6
Access Governance policy
Authentication OAuth 2.1 + mTLS
Rate limit 100 req/min per client
Audit logging Enabled
PII redaction Enabled
Scope enforcement RBAC + tenant-scoped
Write operations Require approval
Agent Operations 16
Outcomes & RCA 8
Network Timeline 7
9
Active Agents
8 findings investigated
Active investigations (24h)
active
A2A collaboration
3
Pending Approvals
Use-Case Agents Purpose-built 16 agents
LLM Pool Model routing 11 models
Agent Orchestrator Live workflow RUNNING
Agent-to-Agent Communication Live inter-agent traffic
Shared Context Via MCP live
Current Finding
F1 · CRIT · 9.2 risk
eBGP prefix leak · PEER-LON1 → AS-XXXX · external peer NOC engaged
Context Shared Across Agents
entity.focus PEER-LON1 + AS-XXXX session
semantic.dim design, protocol, risk, history
drift.scope 341,820 prefixes leaked
owner BGP Policy Agent
root.cause CHG-2026-5510 · deny-clause removed
Human Approvals Required
Execute route-policy rollback on PEER-LON1 from pre-CHG snapshot — awaiting NOC L3 Backbone Engineer approval. Peer NOC informed.
8
Active Findings
surfaced from 4,247 raw alarms (24h)
2
Critical
prefix-leak F1 · L3VPN F3 SLA clock
3
Predicted (pre-failure)
optical · capacity · buffer trend
99.8%
Alarm Reduction Ratio
4,247 raw → 8 actionable findings
9.2
Highest Risk Score
F1 prefix leak · peer-relationship exposure
🔕 Alarm Reduction · last 24h
Alarm Correlator agent · live
Raw ingested
4,247
from EMS · NMS · syslog · probes
Duplicate-collapsed
2,318
60s correlation window
Maintenance-suppressed
487
MW M-2026-0520-A active
Root-cause symptoms
1,234
downstream of 8 findings
Pattern-suppressed
200
learned "no action needed"
8 actionable findings surfaced from 4,247 raw alarms (99.8% reduction). The platform shows the operator the causes, not the noise. Each finding below absorbs anywhere from 8 to 487 raw alarms — see per-finding "Alarm Correlator" entry in evidence trail.
Category
Status All20 Active Drift12 Predicted5 Pattern3
Severity All Critical High Medium
Select a failure mode on the left to see the expected outcome, cause chain, and recommended resolution path.
OUTCOME → CAUSE → FIX
Scope All Sites AMER EMEA APAC Data Centers
Window 24h 7d 30d
Layers Config Changes Drifts Network Pulse Issues
7
Config changes (24h)
4
Active drifts
3
Predicted (pre-failure)
5
Open ServiceNow INCs
42s
Median time-to-detect
Network event timeline Last 7 days · all sites
Config change
Drift
Pulse anomaly
Issue / ticket
Site
REGIONUsers · Detail
Network Score
Executing fix plan…
· 0 of 0 steps
RUNNING
Chain of events 0s elapsed
Agent activity log 0 entries