TECHNICAL CAPABILITY REFERENCE

Find the detail
behind the story.

Find the detail
behind the story.

Search the product capability guide across AI, discovery, detection, collection, access and operations. Use feature IDs to make technical evaluation precise.

Search Demo Company - Command|Link...

Command|Link

3

operator

Alert Spike - WAN Edge Service

Investigation

Nov 5, 2026, 5:04 PM

3

Summary

AI

The alert spike originates from core-router-01 losing its BGP peer at 14:29 UTC. This caused OSPF adjacency failures that cascaded through the WAN Edge service, impacting 5 downstream dependencies.

Services impacted

5

Critical alerts

47

Avg latency

23ms

Throughput

640 Mbps

Findings

AI

Critical

Root cause: BGP peer failure on core-router-01

AI

BGP hold timer expired for peer 10.0.1.1 at 14:29 UTC. This is the earliest event in the cascade and directly caused OSPF adjacency loss. Recommend checking physical link to upstream provider and reviewing BGP keepalive settings.

Warning

Secondary: Possible exploit attempt during outage

AI

IPS flagged CVE-2024-3400 from 203.0.113.42 at 14:31 UTC — 2 minutes after the BGP failure. Attackers commonly probe during routing disruptions. Recommend blocking source IP and reviewing firewall logs for lateral movement.

Ask a follow-up, request deeper analysis, or suggest a hypothesis...

Summary

Components

(8)

Discuss

(3)

Private

Visible to everyone on this investigation

2 open

Command|Intel

6 minutes ago

I've flagged the CVE-2024-3400 exploit attempt as potentially related. Want me to dig deeper into the firewall logs for this source IP?

You

6 minutes ago

Yes — also check if that IP appears in any other event sources in the last 24h

Command|Intel

6 minutes ago

Checked — 203.0.113.42 appears in 3 additional firewall log entries over the past 12h, all port scans on 443/tcp. No lateral movement detected.

Reply... (use @ai)

You

6 minutes ago

Is there a redundant path through fw-edge-west? We should have a failover route configured.

Command|Intel

6 minutes ago

fw-edge-west is online and healthy, but no ECMP or failover route is configured for the BGP peer that failed. The OSPF adjacency to fw-edge-west is intact — this could be a quick mitigation path.

You

5 minutes ago

Confirmed with NOC — the upstream provider had a fibre cut at 14:28. ETA for repair is 2h.

Start a discussion... (or @ai to invoke AI)

Search Demo Company - Command|Link...

Command|Link

3

operator

Alert Spike - WAN Edge Service

Investigation

Nov 5, 2026, 5:04 PM

3

Summary

AI

The alert spike originates from core-router-01 losing its BGP peer at 14:29 UTC. This caused OSPF adjacency failures that cascaded through the WAN Edge service, impacting 5 downstream dependencies.

Services impacted

5

Critical alerts

47

Avg latency

23ms

Throughput

640 Mbps

Findings

AI

Critical

Root cause: BGP peer failure on core-router-01

AI

BGP hold timer expired for peer 10.0.1.1 at 14:29 UTC. This is the earliest event in the cascade and directly caused OSPF adjacency loss. Recommend checking physical link to upstream provider and reviewing BGP keepalive settings.

Warning

Secondary: Possible exploit attempt during outage

AI

IPS flagged CVE-2024-3400 from 203.0.113.42 at 14:31 UTC — 2 minutes after the BGP failure. Attackers commonly probe during routing disruptions. Recommend blocking source IP and reviewing firewall logs for lateral movement.

Ask a follow-up, request deeper analysis, or suggest a hypothesis...

Summary

Components

(8)

Discuss

(3)

Private

Visible to everyone on this investigation

2 open

Command|Intel

6 minutes ago

I've flagged the CVE-2024-3400 exploit attempt as potentially related. Want me to dig deeper into the firewall logs for this source IP?

You

6 minutes ago

Yes — also check if that IP appears in any other event sources in the last 24h

Command|Intel

6 minutes ago

Checked — 203.0.113.42 appears in 3 additional firewall log entries over the past 12h, all port scans on 443/tcp. No lateral movement detected.

Reply... (use @ai)

You

6 minutes ago

Is there a redundant path through fw-edge-west? We should have a failover route configured.

Command|Intel

6 minutes ago

fw-edge-west is online and healthy, but no ECMP or failover route is configured for the BGP peer that failed. The OSPF adjacency to fw-edge-west is intact — this could be a quick mitigation path.

You

5 minutes ago

Confirmed with NOC — the upstream provider had a fibre cut at 14:28. ETA for repair is 2h.

Start a discussion... (or @ai to invoke AI)

Search Demo Company - Command|Link...

Command|Link

3

operator

Alert Spike - WAN Edge Service

Investigation

Nov 5, 2026, 5:04 PM

3

Summary

AI

The alert spike originates from core-router-01 losing its BGP peer at 14:29 UTC. This caused OSPF adjacency failures that cascaded through the WAN Edge service, impacting 5 downstream dependencies.

Services impacted

5

Critical alerts

47

Avg latency

23ms

Throughput

640 Mbps

Findings

AI

Critical

Root cause: BGP peer failure on core-router-01

AI

BGP hold timer expired for peer 10.0.1.1 at 14:29 UTC. This is the earliest event in the cascade and directly caused OSPF adjacency loss. Recommend checking physical link to upstream provider and reviewing BGP keepalive settings.

Warning

Secondary: Possible exploit attempt during outage

AI

IPS flagged CVE-2024-3400 from 203.0.113.42 at 14:31 UTC — 2 minutes after the BGP failure. Attackers commonly probe during routing disruptions. Recommend blocking source IP and reviewing firewall logs for lateral movement.

Ask a follow-up, request deeper analysis, or suggest a hypothesis...

Summary

Components

(8)

Discuss

(3)

Private

Visible to everyone on this investigation

2 open

Command|Intel

6 minutes ago

I've flagged the CVE-2024-3400 exploit attempt as potentially related. Want me to dig deeper into the firewall logs for this source IP?

You

6 minutes ago

Yes — also check if that IP appears in any other event sources in the last 24h

Command|Intel

6 minutes ago

Checked — 203.0.113.42 appears in 3 additional firewall log entries over the past 12h, all port scans on 443/tcp. No lateral movement detected.

Reply... (use @ai)

You

6 minutes ago

Is there a redundant path through fw-edge-west? We should have a failover route configured.

Command|Intel

6 minutes ago

fw-edge-west is online and healthy, but no ECMP or failover route is configured for the BGP peer that failed. The OSPF adjacency to fw-edge-west is intact — this could be a quick mitigation path.

You

5 minutes ago

Confirmed with NOC — the upstream provider had a fibre cut at 14:28. ETA for repair is 2h.

Start a discussion... (or @ai to invoke AI)

AI-001

Model gateway (swap providers without rewiring) Select models and providers through a centralized gateway.

AI & Agentic

AI-002

Anthropic Claude routing (Sonnet, Haiku, Opus)

Access to Anthropic models.

AI & Agentic

AI-003

Google Gemini routing (Flash, Pro)

Access to Google models.

AI & Agentic

AI-004

OpenAI + Azure OpenAI routing Access to GPT models, incl. the enterprise Azure path.

AI & Agentic

AI-005

Azure AI Foundry (DeepSeek) routing Access to a lower-cost reasoning model.

AI & Agentic

AI-006

Local model routing (Ollama) Route workloads to local models through Ollama.

AI & Agentic

AI-007

Per-workload model selection Match model selection to the cost and reasoning requirements of each workload.

AI & Agentic

AI-008

Per-model rate and token limits Protects against runaway spend and provider throttling.

AI & Agentic

AI-009

Input-size guard (200k token cap)

Stops an accidental log dump from becoming a huge bill.

AI & Agentic

AI-010

Cross-provider parameter compatibility

One code path works across all providers.

AI & Agentic

AI-011

Structured / schema-enforced model output

Require structured model responses that conform to the expected output schema.

AI & Agentic

AI-012

Native tool-calling support

Invoke platform functions through native model tool calling.

AI & Agentic

AI-013

Per-request token accounting Track token usage for each AI request.

AI & Agentic

AI-014

Cumulative token tracking per investigation Track cumulative token consumption across an investigation.

AI & Agentic

AI-015

Live token counter exposed as a status query Watch spend while an investigation runs.

AI & Agentic

AI-016

Per-virtual-key dollar budgets Apply spend caps by customer or team.

AI & Agentic

AI-017

Embeddings / vector search / RAG retrieval

Semantic search over the customer's own data.

AI & Agentic

AI-018

MCP tool-server support Standardised way to plug external tools into the agent.

AI & Agentic

AI-019

Automatic conversation compaction

Summarize conversation history to keep long investigations within model context limits.

AI & Agentic

AI-020

LLM-written running summary of an investigation

Preserves findings, hypotheses and data points while dropping bulk.

AI & Agentic

AI-021

Per-step context windowing Each reasoning step only sees what it needs.

AI & Agentic

AI-022

Tool-result truncation Bound tool-response size to protect conversation context.

AI & Agentic

AI-023

Token estimation before calling the model Estimate token requirements before submitting a model request.

AI & Agentic

AI-024

Tool: search_events The agent can search the customer's events by keyword, time, severity and source.

AI & Agentic

AI-025

Tool: get_metrics

The agent can pull time-series data for a device or interface.

AI & Agentic

AI-026

Tool: get_top_talkers

The agent can find the busiest source IPs.

AI & Agentic

AI-027

Tool: aggregate_metrics The agent can compute averages, maxima, minima and sums itself.

AI & Agentic

AI-028

Tool: search_logs Full-text search across all log content.

AI & Agentic

AI-029

Tool: get_device_summary Events, alert counts and metric baselines for one device in one call.

AI & Agentic

AI-030

Tool: ip_lookup (geo + ASN) The agent can find out where an address is and who owns it.

AI & Agentic

A few good questions

Get clear
on the details.

Can we import every spreadsheet or portal automatically?

Collection and onboarding depend on the source. Validate each connection and mapping; do not assume a universal spreadsheet or portal importer. Operational knowledge can be added through the supported context and operator-guidance workflows.

Your next operational advantage

Put AI to work.
Leave the sprawl behind.

Bring your stack and a recent incident.
See what your team can simplify.