datadog-mcp 5.4.0 → 5.5.0
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.
- package/README.md +11 -2
- package/dist/index.js +685 -29
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -122,8 +122,8 @@ When running with `--transport=http`:
|
|
|
122
122
|
| `monitors` | list | Alerting | List monitors with optional filters | `monitors_read` |
|
|
123
123
|
| `monitors` | get | Alerting | Get monitor by ID | `monitors_read` |
|
|
124
124
|
| `monitors` | search | Alerting | Search monitors by query | `monitors_read` |
|
|
125
|
-
| `monitors` | create | Alerting | Create a new monitor | `monitors_write` |
|
|
126
|
-
| `monitors` | update | Alerting | Update an existing monitor | `monitors_write` |
|
|
125
|
+
| `monitors` | create | Alerting | Create a new monitor; `config` is validated against a typed schema covering documented options (notifyNoData, renotifyInterval, thresholds, …) — unknown keys surface in `warnings` | `monitors_write` |
|
|
126
|
+
| `monitors` | update | Alerting | Update an existing monitor; same validated schema as `create`; partial configs accepted; validation errors short-circuit before any HTTP call as `EINVALID_MONITOR_CONFIG:` | `monitors_write` |
|
|
127
127
|
| `monitors` | delete | Alerting | Delete a monitor | `monitors_write` |
|
|
128
128
|
| `monitors` | mute | Alerting | Mute a monitor | `monitors_write` |
|
|
129
129
|
| `monitors` | unmute | Alerting | Unmute a monitor | `monitors_write` |
|
|
@@ -135,6 +135,15 @@ When running with `--transport=http`:
|
|
|
135
135
|
| `dashboards` | delete | Visualization | Delete a dashboard | `dashboards_write` |
|
|
136
136
|
| `logs` | search | Logs | Search logs with query syntax and filters | `logs_read_data`, `logs_read_index_data` |
|
|
137
137
|
| `logs` | aggregate | Logs | Aggregate log data with groupBy | `logs_read_data` |
|
|
138
|
+
| `logs_pipelines` | list, get | Logs Config | Inspect log processing pipelines and their processors | `logs_read_config` |
|
|
139
|
+
| `logs_pipelines` | create, update, delete, reorder | Logs Config | Author pipelines and processor chains | `logs_write_config` |
|
|
140
|
+
| `logs_pipelines` | get_order | Logs Config | Read pipeline evaluation order | `logs_read_config` |
|
|
141
|
+
| `logs_indexes` | list, get | Logs Config | Inspect indexes (filter, retention, Flex tier, exclusion filters); `create`/`delete` are UI-only per Datadog and not exposed | `logs_read_config` |
|
|
142
|
+
| `logs_indexes` | update, reorder | Logs Config | Update index filter/retention/quota and reorder evaluation | `logs_write_config` |
|
|
143
|
+
| `logs_indexes` | get_order | Logs Config | Read index evaluation order | `logs_read_config` |
|
|
144
|
+
| `logs_archives` | list, get | Logs Config | Inspect log archives (S3 / GCS / Azure destinations); per-provider credential fields are forwarded unchanged | `logs_read_archives` |
|
|
145
|
+
| `logs_archives` | create, update, delete, reorder | Logs Config | Manage archive destinations; `destination.type` validated against `s3 | gcs | azure_storage` before SDK call | `logs_write_archives` |
|
|
146
|
+
| `logs_archives` | get_order | Logs Config | Read archive evaluation order | `logs_read_archives` |
|
|
138
147
|
| `metrics` | query | Metrics | Query timeseries data | `metrics_read`, `timeseries_query` |
|
|
139
148
|
| `metrics` | search | Metrics | Search for metrics by name | `metrics_read` |
|
|
140
149
|
| `metrics` | list | Metrics | List active metrics | `metrics_read` |
|