Skip to main content
Data Infrastructure Insights

Inventory environment and collection health

Contributors netapp-alavoie
PDFs

Use this recipe to understand whether DII's acquisition units and configured data sources are connected, reporting, and collecting successfully.

Note The DII MCP is a Preview feature and is therefore subject to change.

Prerequisites

  • Access to acquisition-unit and collector tools.

  • An optional acquisition-unit or collector name to narrow the investigation.

Tools used

  • AcquisitionUnitsService_getAcquisitionUnits

  • AcquisitionUnitsService_getAcquisitionUnitByUuid

  • CollectorService_getDataSources

  • CollectorService_getDataSourceById

  • CollectorService_getDataSourceTypes

Starter prompt

Review my DII collection environment. Summarize acquisition units by connection status and reporting freshness, then summarize configured data sources by acquisition status and vendor. Highlight acquisition units that never reported, units with no assigned collectors, failed collectors, and stale successful acquisitions. Do not display IP addresses, UUIDs, or credentials.

Agent workflow

  1. List all acquisition units.

  2. Classify each AU using both connection status and lastReported.

  3. Count assigned data sources per AU.

  4. List all configured data sources.

  5. Group collectors by status, vendor, model, and AU.

  6. Identify:

    • Disconnected or heartbeat-failed AUs

    • Connected AUs that never reported

    • AUs with zero data sources

    • Failed collectors

    • Collectors with no successful acquisition

    • Successful collectors whose last acquisition is unexpectedly old

  7. Retrieve full AU or collector details only for the exceptions.

  8. Return a prioritized summary and clearly state the freshness threshold used.

Interpretation

Use these distinctions:

  • Connected and reporting: the AU is connected and has a recent lastReported value.

  • Connected but never reported: connectivity exists, but successful telemetry reporting is not established.

  • Heartbeat failed: investigate the AU host, network path, and service.

  • Collector failed: inspect the collector's recent poll activity, package status, configuration, and last successful acquisition.

  • No assigned collectors: this can be intentional; verify before treating it as a fault.

The supported data source type catalog describes products DII can collect. It does not prove that those products are configured in the tenant.

Suggested output

  1. Executive summary

  2. Acquisition-unit status counts

  3. Collector status counts

  4. Exceptions ranked by operational impact

  5. Recommended checks

  6. Data limitations

Limits and privacy

  • Avoid returning AU UUIDs, IP addresses, private hostnames, or collector credentials.

  • A status value alone does not establish data freshness.

  • Retrieve detailed configuration only for named exceptions.

Follow-up prompts

Inspect the failed collector named example-array. Summarize recent poll activity and collection-package failures without showing credentials or private addresses.

Which acquisition units have not reported within the last 30 minutes, and which collectors depend on them?

Compare configured collector vendors with the DII supported data source type catalog.

Back to recipes