Remediation
How QUARK recommends fixes, and how remediation suggestions are structured.
Every QUARK finding ends with the question that matters: what should we do about it? Remediation recommendations are QUARK's answer.
What a recommendation looks like
Recommendations are specific to the finding and your environment — not generic advice:
Finding: Datastore DS-PROD will reach 90% capacity in ~11 days.
Recommended actions:
- Three powered-off VMs on DS-PROD hold 412 GB of thin-provisioned disk — reclaim if no longer needed (list attached).
- Snapshots older than 30 days consume 108 GB across 7 VMs — consolidate.
- If growth continues at the current 2.1 GB/day trend, plan an expansion of at least 500 GB this quarter.
Each step lists the exact objects involved, the expected effect, and the risk level of the change.
Risk levels
| Level | Meaning | Examples |
|---|---|---|
| Safe | No service impact expected | Clearing logs, consolidating snapshots |
| Caution | Brief or partial impact possible | Service restart, failover test |
| Planned change | Should go through change management | Firmware updates, capacity expansion |
QUARK recommends — you decide
QUARK does not execute changes against your infrastructure. Recommendations are carried out by your team, through your normal change process. To make that easy:
- Copy as ticket — export the recommendation, evidence, and affected objects into a ticket in the ticketing system.
- Runbook links — if your team maintains runbooks, link them to finding types under Settings → Runbooks; matching findings will surface your own procedure alongside QUARK's suggestion.
Feedback loop
Mark each recommendation as applied, modified, or not applicable when closing a finding. QUARK uses this to rank future recommendations — the fixes your team actually uses rise to the top.