Skip to main content
Data Infrastructure Insights

DII MCP operational recipes

Contributors netapp-alavoie

Recipes combine multiple read-only DII tools into repeatable infrastructure workflows. Use them as starting points and replace fictional resource names with values from your tenant.

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

Choose a workflow

Goal Recipe Primary DII surfaces

Validate collection coverage and freshness

Inventory environment and collection health

Acquisition units, data sources

Prioritize active infrastructure issues

Assess storage health

Alerts, monitors, logs, objects

Find pools approaching capacity pressure

Identify capacity risk

Object metadata, grouping, time series

Check Kubernetes collection component versions

Check Kubernetes collector currency

Kubernetes collectors

Investigate a slow volume or workload

Troubleshoot performance

Object metrics, alerts, logs

Review routing and suppression safely

Review notification posture

Rules, targets, maintenance windows

Standard investigation pattern

  1. Clarify the resource scope and time range.

  2. Discover available types.

  3. Retrieve metadata before using dynamic fields.

  4. Query a bounded time window.

  5. Correlate independent signals.

  6. Distinguish observed facts from inferences.

  7. Report limitations and recommended follow-up.

Safety

  • These recipes use read-only tools.

  • Keep time windows to 30 days or less.

  • Omit credentials, private addresses, UUIDs, raw webhook endpoints, and unnecessary log payloads.

  • Confirm high-impact operational actions outside the MCP workflow.