Asama plans the fix. You approve it.
For each incident, Asama writes a node-specific fix and the code that verifies it, following your maintenance policy. Nothing runs until you approve it. Rollback is ready before the first step, and every run improves the next plan.
Read-only by default · No training on your data · SOC 2 Type II
How the remediation loop works
Detection and diagnosis hand over the root cause and its evidence. From there it’s one loop: Asama plans, you approve, the workflow runs and verifies, and every run improves the next plan.
Your fleet is heterogeneous. The same server model runs different firmware and BIOS versions from one rack to the next, so a single automation never fits every host. That leaves your team maintaining runbooks and scripts for every variation, and rewriting them each time something changes.
A plan, not a suggestion
Asama starts from the diagnosis, the root cause and its evidence, and plans for this incident on this node, using its live configuration, firmware and versions, and what worked in past runs. Each plan is sequenced into phases with the exact changes and commands.
- Writes the fix and the code that verifies it
- Plans for each node’s firmware and BIOS
- Success and failure paths set before it runs
From 3 past db-tier journald fixes
Planned from
Journal 1.9G, disk 91% full
systemd 252, no drop-ins
Fix
journald.conf: Verification · runs after each batch
Built against your policy
Maintenance windows, batch limits and environments are inputs to the plan, not something you apply afterwards.
- Respects your windows and batch limits
- Holds approved plans for the next window
- Announces the change to workload owners
Held by the maintenance orchestrator
Maintenance policy
Tue 14 Oct · 02:00–04:00 PDT
Weekly db-tier window
2 hosts at a time
db-tier batch limit
Workload owners
postgres · pg-orders-replica-2
lab-sf-db07 · Data Platform
You approve, or you change it
Nothing runs until you approve it. Approve the plan as it stands, or edit the code and ask Asama to revise it and explain its choices.
- Flags risks and policy conflicts
- Saves your edits for the next plan
- Run it now, or schedule it
1 risk flagged · 1 edit
Risk flagged
Restarting journald briefly pauses log shipping.
Prepare
Executed, verified, escalated
A durable execution workflow applies the fix in batches and runs the verification code after each one. Rollback is computed before the first step.
- Rolls back on a failed check
- Alerts you and brings a revised plan
- Each run improves the procedure library
5 hosts · batch size 2
Hosts
lab-sf-db05
VerifiedJournal at 186.0M.
02:11lab-sf-db06
Rolled backCheck failed at 488.0M. Rolled back.
02:17A vendor drop-in overrides SystemMaxUse. The revised plan waits for your review.
FAQ
No. Asama’s agent writes the plan and brings in your team to review it. Once you approve the plan, the agent hands execution to a workflow engine that acts as the maintenance orchestrator, and the workflow engine runs the change within your change management process.
They stay in charge. Asama imports them as skills into its platform, builds every plan against your maintenance windows, batch limits and environments, and flags any policy conflicts before you approve. The workflow engine holds approved plans until the next allowed window.
Yes. Edit the code yourself, or ask Asama to revise the plan and explain its choices. Nothing runs until you approve it, and your edits are saved so future plans for similar issues start from them.
The workflow stops at the last verified step and rolls back, using the rollback Asama computed before the first step. You’re alerted straight away, and Asama drafts a revised plan that comes back to you for review.
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.