DII MCP operational recipes
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.
|
|
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 |
Acquisition units, data sources |
|
Prioritize active infrastructure issues |
Alerts, monitors, logs, objects |
|
Find pools approaching capacity pressure |
Object metadata, grouping, time series |
|
Check Kubernetes collection component versions |
Kubernetes collectors |
|
Investigate a slow volume or workload |
Object metrics, alerts, logs |
|
Review routing and suppression safely |
Rules, targets, maintenance windows |
Standard investigation pattern
-
Clarify the resource scope and time range.
-
Discover available types.
-
Retrieve metadata before using dynamic fields.
-
Query a bounded time window.
-
Correlate independent signals.
-
Distinguish observed facts from inferences.
-
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.