Public sample report
See what the workload evidence can tell you.
Example workflow — not a customer case study.
This example uses fictional VMware, Proxmox, KVM and Kubernetes data. It shows resource allocation, available observations and the questions to resolve before a target decision. These are separate workloads, not before-and-after pairs.
Demonstration data only. No customer infrastructure or live system is connected.
Infrastructure overview
Fictional workloads: 4
Observation window: Not available
N/A means unavailable, not zero. Field presence does not establish representative time coverage.
Allocation and observed utilisation
| Workload | Platform | Allocated vCPU | Allocated RAM (GiB) | CPU snapshot | RAM snapshot | Signal completeness |
|---|---|---|---|---|---|---|
| prod-payments-api-01 | VMware | 4 | 8 | 18.4% | 61.2% | Partial |
| prod-erp-db | Proxmox | 8 | 16 | 34% | 75% | Partial |
| prod-web-02 | KVM/libvirt | 2 | 4 | N/A | 48.5% | Limited |
| prod/payments-api-7f8cc9d78b-x42pz | Kubernetes | 0.6 | 0.875 | N/A | N/A | Limited |
Completeness reflects the report’s available CPU/RAM fields. It is not confidence in a final sizing decision. Kubernetes allocations are resource requests; they are not measured consumption.
Coverage, risks and prerequisites
The fixtures contain no observation period or time series. CPU/RAM p95, p99, peak behaviour and business-cycle coverage are unavailable. A short measurement never guarantees a suitable target size.
VMware guest-memory observations and Proxmox memory accounting have different meanings. VMware datastore pressure is also different from workload disk utilisation. A shared percentage label does not make these measurements comparable.
Before any pilot, confirm application ownership, dependencies, backups, acceptance criteria, a maintenance window and a rollback plan with the team responsible for the change.
Disk I/O, network throughput, energy, application performance and anomaly history: N/A. No savings or energy reduction is calculated.
Decision: further review required
This evidence can frame the next observation and technical review. It does not approve a target configuration or authorise a production change.
Post-change validation is not available yet
Automatic comparison of a VMware baseline with a mapped Proxmox workload is not implemented. This sample does not claim a before-and-after result. The current offer supports observation and decision preparation before change.
Review the evidence needed for your migration case.
Share the source platform, target and approximate workload count. We confirm scope before any production processing starts.
Review a migration case