@infinitedusky/indusk-mcp 1.14.1 → 1.14.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -35,9 +35,19 @@ Dash0 provides access to your OpenTelemetry data — logs, traces, and metrics
35
35
 
36
36
  The MCP server provides 23 tools. The key ones for debugging:
37
37
 
38
+ **Dataset (MANDATORY)**: Every Dash0 MCP call MUST include a `dataset` parameter. Never omit it. Use this lookup table:
39
+
40
+ | Context | Dataset ID |
41
+ |---------|-----------|
42
+ | local / dev / default | `dev` |
43
+ | production | `chitin-production` |
44
+ | demo | `dash0-demo` |
45
+
46
+ **Default**: `dev` (local development). When the user says "check production" or "what's happening on prod", use `chitin-production`. If unsure which environment the user means, ask — do not guess, do not omit.
47
+
38
48
  ### Logs
39
49
  - **`getLogRecords`** — Query logs with filters, time range, pagination. Returns summary table.
40
- - **Dataset**: check `env/components/dash0.env` for the dataset per profile (local, staging, production). If no composable.env component exists, check `.indusk/extensions/dash0/.env` for a `DASH0_DATASET` value. If neither exists, ask the user which dataset to use and remember it for the session.
50
+ - `dataset`: **required** see lookup table above
41
51
  - `timeRange` requires ISO timestamps: `{"from": "...", "to": "..."}`
42
52
  - `filters`: `[{"key": "service.name", "operator": "is", "value": "game-server"}]`
43
53
  - `logAttributeKeys`: specify which attributes to show in the table (e.g. `["service.name", "otel.scope.name"]`)
@@ -46,12 +56,12 @@ The MCP server provides 23 tools. The key ones for debugging:
46
56
  - **`getLogCorrelations`** — Find patterns and correlations in logs
47
57
 
48
58
  ### Traces
49
- - **`getSpans`** — Search for spans (traces) with filters and time range
59
+ - **`getSpans`** — Search for spans (traces) with filters and time range. `dataset`: **required**.
50
60
  - **`getTraceDetails`** — Get full trace tree by trace ID, including hierarchy, events, and comparison to similar spans
51
61
  - **`getSpanCorrelations`** — Find patterns in spans
52
62
 
53
63
  ### Services
54
- - **`getServiceCatalog`** — All services with RED metrics (requests, errors, duration) and dependency map
64
+ - **`getServiceCatalog`** — All services with RED metrics (requests, errors, duration) and dependency map. `dataset`: **required**.
55
65
  - **`getServiceDetails`** — Deep dive into a single service
56
66
 
57
67
  ### Metrics
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@infinitedusky/indusk-mcp",
3
- "version": "1.14.1",
3
+ "version": "1.14.3",
4
4
  "description": "InDusk development system — skills, MCP tools, and CLI for structured AI-assisted development",
5
5
  "type": "module",
6
6
  "files": [