Know what changed, and when
Inventory → Changelog shows every hardware change across your fleet, from the last 24 hours up to 15 days.
Asama traces a causal chain through hosts, VMs, storage and network, and backs each link with the state it observed.
Read-only by default · No training on your data · SOC 2 Type II
Asama keeps the state of your entire infra stack as it changes, so a past window can still be queried. For every symptom it builds a list of hypotheses, tests each one against the knowledge graph and the timeline, and traces the causal chain. Hypotheses the evidence rules out across the topology are dropped.
Most incidents are hard to debug. Transient issues clear on their own, and by the time anyone logs in the evidence is gone. Cross-layer issues surface in one layer while the cause sits in another, so the obvious suspect is rarely the real one. And finding the root cause often takes people from several teams, each looking at their own tools, piecing the story together by hand.
A baseline drifts, or someone on your team asks. Either way, the symptom names the layer it surfaced in. Asama helps you find the exact cause.
Incoming symptom
Today · 13:44Reports on reporting-vm are taking minutes instead of seconds.
Raised by the finance analytics team · #infra-help
Asama reads the dependency graph and the change history to produce every path that could have produced this symptom.
Dependency path
Hypotheses
6 generated · 0 testedvCPU contention on lab-sf-30
VirtualizationKernel update on lab-sf-30, 3 days ago
KernelPacket loss on the NFS path
NetworkStorage degradation under /dev/md0
+ 2 more
14 graph edges traversed · 3 changes in the last 7 days
Each hypothesis is tested against the timeline and the stored state. What the evidence contradicts is discarded, and the discard is shown.
Ruled out by evidence
5 of 6 discardedSteal time stayed at 0.4%; host CPU peaked at 31%.
0 drops; RTT to lab-sf-31 steady at 0.21 ms.
Consistent with the evidence
Degraded, with discards from 13:36, 2 min before latency rose.
What is left is returned with the evidence behind it: array state, active processes, load, so the reasoning can be checked rather than trusted.
Cause
Degraded RAID1 /dev/md0 on lab-sf-31, under an active discard job.
Evidence
/dev/md0 in state [4/3] [UUU_]
fstrim running against /dev/md0
Load on lab-sf-30 peaked, now falling
LoadInventory → Changelog shows every hardware change across your fleet, from the last 24 hours up to 15 days.
Every investigation shows how fresh its data is, and accounts for data that’s out of range.
Investigations weigh each anomaly’s trend: Worsening, Recovering, Stable or Recurring.
No. Investigation runs on read-only access, so Asama never changes your hosts while it works out the cause. Credentials stay in your secret management vault inside your own infrastructure.
Yes. Asama keeps the state of your full infra stack as it changes, so a past window can still be queried, even after the issue has cleared and the evidence is gone from the host.
Every investigation report is backed by evidence, from live data or from past state, and shows its sources. You can check each claim yourself before you act on it.
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.