> This page is for version Latest (default). > For other versions, use one of these documentation indexes: > - Latest (default): https://docs.nvidia.com/fleet-intel/latest/llms.txt > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.nvidia.com/fleet-intel/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/fleet-intel/_mcp/server. # Reports On the **Reports** tab, you can run reports on your [Inventory Report](#inventory-report), [Error Report](#error-report) and a [MTBI Report](#mtbi-report) in your fleet. ![Report overview.](/fleet-intel/_fern-files/_img/f85ebdf52c57fdf395b9a0bcc82e5e56327cb19338a4f53c19bab945de7fdc1f.webp) When you select a report, you can specify a time range, Compute Zone, and Node Group, or use the **Filter Machines by Tag** option. Node Group and Compute Zone are optional; machines can also be filtered by [Tags](/fleet-intel/groups-tags#tags). ![Report overview.](/fleet-intel/_fern-files/_img/29c90a18202be5d2849794e7dbca8132ad07fa1c170b98bbda1889df9d7aa70f.webp) ## Inventory Report ![Example Inventory Report.](/fleet-intel/_fern-files/_img/0977e13382f0ea261f4aafa7247226ec71c4868e961bf8a72559b365030ffe85.webp) After generating the Inventory report, you can download the inventory report as a CSV file using the button in the upper right. Use the **Edit report** button to change the report selection criteria. In addition to standard CSV downloads, Fleet Intelligence can provide **signed inventory reports** — cryptographically signed by NVIDIA so that any third party can verify the report has not been tampered with and was generated by the NVIDIA Fleet Intelligence service. Signed reports are suited for regulatory compliance, audits, and supply-chain verification workflows. A signed report is delivered as a `.zip` archive containing two files: * The inventory data as a `.csv` file. * A Sigstore-format signature bundle (`.sig.bundle`) that covers the full CSV payload and the generation timestamp. The signature can be verified with the open-source [cosign](https://github.com/sigstore/cosign) tool directly. ### Downloading a Signed Report In the Fleet Intelligence dashboard, navigate to the **Reports** tab and select the **Inventory Report** option. Generate the Inventory Report as usual. When you click **Download**, you are prompted to choose between an unsigned `csv` file and a signed report `zip` archive. ![Downloading a Signed Report.](/fleet-intel/_fern-files/_img/fd3caccd2739c7b28aca94f12537473b2ef0e55c612ebfcd37dd6c7934739e91.webp) Extract the archive to obtain the `.csv` and `.sig.bundle` files before verifying. If you have the nvfleetint CLI installed you can use it to create, download inventory and error reports. To generate an inventory report using the CLI use the following (after setting up authentication). For complete details, refer to the [NV Fleet Intelligence CLI documentation](https://docs.nvidia.com/fleet-intel/client/overview/) ```bash nvfleetint report inventory --format csv --signed --output-path inventory-report.zip ``` ### Verifying a Signed Report #### Verification with the Fleet Intelligence CLI If you have the nvfleetint CLI installed you can use it to verify signed inventory reports. Use the following command to verify the report. ```bash unzip inventory-report.zip -d verify-report cd verify-report nvfleetint report verify \ --csv ./*.csv \ --bundle ./*.sig.bundle ``` For complete details, refer to the [NV Fleet Intelligence CLI documentation](https://docs.nvidia.com/fleet-intel/client/overview/) #### Third-Party Verification with Cosign Because the signature bundle uses the [Sigstore](https://www.sigstore.dev/) format, anyone with the `cosign` tool and the NVIDIA Fleet Intelligence public key can independently verify a report. Cosign v3.0.0 or newer is required — v3 introduced the bundle format used for signing and changed several flag defaults; earlier versions will reject the bundle. Download the NVIDIA Fleet Intelligence public key (PEM format) from the Fleet Intelligence API endpoint at [https://api.fleet-intelligence.nvidia.com/.well-known/signing-key.pub](https://api.fleet-intelligence.nvidia.com/.well-known/signing-key.pub): ```bash cosign verify-blob \ --key ../signing-key.pub \ --bundle ./*.sig.bundle \ --insecure-ignore-tlog \ ./*.csv ``` A successful verification prints `Verified OK`. Why **--insecure-ignore-tlog**? NVIDIA does not publish report signatures to a public transparency log. The flag's name is misleading: with this flag set, verification remains cryptographically sound for our threat model and should not be misread as a security concern. What "Verified OK" means If verification passes, the user has cryptographic proof that: * NVIDIA Fleet Intelligence produced these exact CSV bytes. * They have not been altered since signing. ### Key Rotation Model > **Note** > > Key rotations should occur rarely and only in the event of a compromised key. Under the current key rotation model, NVIDIA only provides the latest key. Any report signed with a historical key continues to verify with the historical key, but new reports are signed by the current key. Customers will be notified of key rotation and should take the following actions: 1. Re-download the same report from the API — the system regenerates byte-identical CSV bytes (deterministic regeneration is a design constraint) with a fresh signature under the new key. 2. Re-fetch the public key from [https://api.fleet-intelligence.nvidia.com/.well-known/signing-key.pub](https://api.fleet-intelligence.nvidia.com/.well-known/signing-key.pub). 3. Re-run the verification command. Customers should re-download immediately on receiving a rotation notice and re-issue the artifact to any concerned parties. Anyone encountering a failed verification should ask the NVIDIA customer for a refreshed copy before concluding the report is forged. > **Note** > > Exercise caution when verifying signed reports. > Always confirm that you are using the latest public key. ### Installing Cosign Install `cosign` on the system where you want to perform third-party verification. For Linux and macOS installation, instructions are available at [https://github.com/sigstore/cosign](https://github.com/sigstore/cosign). For Windows, refer to the following instructions. **Windows** Choose one of the following methods. *PowerShell (direct download)*: ```powershell Invoke-WebRequest ` -Uri "https://github.com/sigstore/cosign/releases/latest/download/cosign-windows-amd64.exe" ` -OutFile "cosign.exe" ``` *WinGet*: ```powershell winget install Sigstore.Cosign ``` *Scoop*: ```powershell scoop install cosign ``` After installation, confirm `cosign` is available: ```bash cosign version ``` ## Error Report ![Example Error Report.](/fleet-intel/_fern-files/_img/ccab4e744e939ea0e45c8c38c3881613f1e8f03bff170b6a13301e634b05ac70.webp) Use the **Edit report** button to change the report selection criteria. The Error report allows dynamic selection of the severities to display. > **Note** > > The Error report is currently only downloadable using the CLI. ## MTBI Report Mean Time Between Interruption (MTBI) report. The MTBI report generation also allows you to filter by GPU type. ![Example MTBI report.](/fleet-intel/_fern-files/_img/d3adff0a638535a72dbc57faa4bf0019a96e30732349c9050c8281469d3eeebe.webp) After generating the MTBI report, you can download the MTBI report as a CSV file using the button in the upper right. Use the **Edit report** button to change the report selection criteria.