Troubleshooting Report

After the scan completes, clicking Download Offline Report generates a standalone .html file containing a full summary of the scan results. This report is designed primarily to support troubleshooting of scan success during deployment.

It allows you to review which VMs failed, investigate why, and collaborate with application or infrastructure teams using filtered exports.

Offline report HTML showing summary ring charts, filtering, and detailed scan status

Purpose

The Offline Report is intended to validate scan completeness and identify issues preventing successful data collection. It is not designed to show transformation or migration readiness results.

Key Features

  • Filter across multiple categories at once
    Quickly isolate VMs by scan result, vCenter, operating system, power state, error reason, and more.

  • Export filtered VMs to CSV
    Export any filtered subset of VMs as a .csv file — ideal for sharing with application owners or remediation teams.

  • Detailed error visibility
    Error messages shown are specific and contextual — not generic — to help with rapid diagnosis.

  • Interactive hover tooltips
    Hovering over icons displays extended descriptions, including actual values (e.g., CPU usage, configured thresholds).

  • Breakdown by scan phase
    Icons show whether data was collected at the VMware (hypervisor), guest OS (VM), or pre-scan check level.

  • OS version visibility
    OS details are shown per-VM to assist in targeting platform-specific fixes (e.g., Linux credential issues).

Icon Legend

Icon Type Meaning
Power State Shows whether the VM was powered on or off at the time of scan.
Scan Success Green = scan successful, Amber = partial, Red = failed.
VMware Metrics Indicates whether hypervisor-level metrics (e.g., CPU, memory) were collected.
VM Metrics Shows whether guest-level data (OS, installed software, DB presence) was collected.
Prescan Checks Shows results of threshold-based checks (e.g., CPU/memory/disk usage).
ℹ️
Hovering over each icon displays detailed context, including collected values and configuration thresholds.

Using the Offline Report

After downloading the .html report file:

  1. Open the file in a browser
    Double-click the file to open it in Chrome, Edge, or Firefox. No internet connection is required — everything runs locally in your browser.

  2. Filter the VM list
    Use the interactive controls at the top of the report to filter results by:

    • Scan status (e.g. completed, partial)
    • vCenter or host name
    • OS type
    • Power state
    • Scan phase success (VMware, guest OS, prescan)
    • Error categories or specific messages

    As you adjust filters, the summary charts and VM list will automatically update.

  3. Export filtered results to CSV
    After applying your desired filters:

    • Click the “Export” button (located above the VM table).
    • A .csv file will be generated in your browser, containing only the filtered VMs.
ℹ️

You can also use the CSV as an import for the Scan step to streamline scope management—just remove any VMs you don’t want included in the scan.

The export is performed entirely in the browser. No data is uploaded externally. CSV output reflects the currently visible table rows and respects all active filters.

Special Notes

ℹ️

A CollectionError column appears in the table to summarize any errors that prevented scan success. This field aggregates both prescan failures and collection failures in a single place.

Grey database icons in the VM Metrics column indicate that no database was detected on the VM — it does not mean that a database was skipped or failed to scan. A tooltip will be added in a future update to clarify this visually.

Prescan thresholds are dynamic. For example, if the memory usage threshold is set to 80% in the DMC settings, this value will appear in the tooltip when hovering over the prescan result. This ensures the troubleshooting screen always reflects the actual configuration in use.

Use Cases

  • Filter for partial or failed scans to identify VMs needing remediation.
  • Export only affected VMs to CSV for follow-up by infrastructure or application teams.
  • Review prescan values and thresholds to understand why a VM was skipped or failed.
  • Maintain a record of scan health during deployment for audit or QA purposes.
⚠️
This report supports scan diagnostics only. Transformation strategy and migration recommendations are available through the Dr Migrate SaaS platform after results are uploaded.