Asama

The reliable way to know what's wrong across your infrastructure

Plain-language answers grounded in live data, with sources you can check and actions you approve.

Read-only by default · No training on your data · SOC 2 Type II

Why is latency up on the dc1 core links?

Asama Copilot · answering

The cause is a degrading optic on dc1-core-02 port Et49/11, which started logging CRC errors at 09:122. Traffic shifted onto the dc1-core-01 uplinks, which are now at 92% utilisation3, and that is where the latency shows up.

Cause

Degrading optic on dc1-core-02 Et49/1

Symptom

p95 latency on dc1 core links up from 0.4 to 3.8 ms

Evidence

Where Metric Now Source
dc1-core-02 Et49/1 CRC errors / min 1,240 2
dc1-core-02 Et49/1 Rx power −11.8 dBm 1
dc1-core-01 uplinks Utilisation 92% 3
dc1 core links p95 latency 3.8 ms 2

Checking other optics from the same batch

Sources 1 Inventory optic serials and DOM readings 2 Monitoring interface counters and latency 3 Topology dc1 core paths

From question to fix, in one place

Copilot is a conversational interface to your infrastructure. Ask a question in plain language and it answers from live monitoring, inventory and topology data, shows the sources behind every claim, and helps you act on what it finds.

The usual route to an answer means jumping between dashboards, spreadsheets, CLI sessions and ticket queues, then piecing the story together with a cross-functional team. Getting to the answer is the slow part.

Start your day with answers, not alerts

Asama continuously tracks hardware faults, anomalies, performance drift and vulnerabilities. Copilot explains what it finds, helps you investigate, and plans remediation while keeping your experts in the loop.

  • Faults, anomalies, drift and vulnerabilities in one briefing
  • Each issue explained, with likely cause and impact
  • Remediation plans your experts review and approve

Morning briefing

Mon 19 Oct · 08:00

3 things need your attention today

  • 1 Fault

    Optic degrading on dc1-core-02 Et49/1, CRC errors rising

    dc1-core-02

    Open conversation →
  • 2 Drift

    BIOS behind the fleet standard on 3 Dell R750s

    dc1-r750-04, -09, -12

    Open conversation →
  • 3 Vulnerability

    BMC firmware affected by a published advisory

    6 hosts in dc2

    Open conversation →

Ask your inventory and topology anything

Find what you have, where it sits and what depends on it, without writing queries or opening a new dashboard. Copilot answers from a live, topology-aware knowledge graph. No need to manually update your inventory.

  • Find devices by model, firmware, location or health
  • Trace upstream and downstream dependencies
  • Check blast radius before you make a change

Which Dell R750s in dc1 are on firmware older than 2.1?

3 of 14 Dell R750s in dc1 are on firmware older than 2.1.

Host Rack Firmware Health
dc1-r750-04 A12 1.9.2 OK
dc1-r750-09 B03 2.0.1 OK
dc1-r750-12 B07 1.8.4 Warning

Dependencies · dc1-r750-12

dc1-leaf-03dc1-core-02 dc1-r750-12 pg-orders-01kafka-broker-2
Upstream Downstream

Run the closed loop in one conversation

Detection, investigation and remediation happen in the same thread, so context never gets lost between tools or handoffs.

  • Pick up any thread where someone left off
  • Every step logged with an audit trail
  • Backed by evidence

Thread

dc1 core links: latency up

Closed

4 steps · audit trail on

  1. Detected

    09:12

    CRC errors on dc1-core-02 Et49/1

    Done
  2. Investigated

    09:16

    Cause: degrading optic on Et49/1

    Done
  3. Remediated

    09:41

    Optic replaced after approval by infra on-call

    Done
  4. Verified

    09:48

    p95 latency back to 0.4 ms

    Verified

Raise the ticket, brief the stakeholder

Once the fault is established, Copilot takes care of the follow-up. It drafts tickets with the evidence attached and writes incident summaries pitched at whoever needs to read them.

  • Tickets pre-filled with cause, impact and evidence
  • Summaries for engineers, leadership or support teams
  • Nothing is sent or raised without your approval

Follow-up · dc1 core latency

2 drafts
Ticket draft NET-4821 · P2

Replace degrading optic on dc1-core-02 Et49/1

Cause
Optic Rx power down to −11.8 dBm, CRC errors from 09:12
Impact
dc1 core p95 latency 0.4 → 3.8 ms

Evidence attached

CRC countersDOM readingsCore paths
Summary for Leadership
  • Internal network latency in dc1 rose this morning.
  • The cause is one failing optical module.
  • A replacement is planned; no action needed from you.
Approve and send

FAQ

See Asama on your own fleet

Bring one recurring problem your current tooling hasn’t solved. We’ll show you how Asama detects it, finds the cause, and plans the fix.