monitoring.metrics.resourcesList the resources that record metrics, and the apps that ship logs
GET /monitoring/api/resourcesIAM monitoring:ListMetricsRead
Request syntax
GET /monitoring/api/resourcesResponse
200 with { resources, apps }: resources is each resource of the organization with resourceType, resourceId, label (what a person calls it), href (its console page) and metrics (the names it records), terminated machines included; apps is each app as { id, name }.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow monitoring:ListMetrics on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud monitoring metrics resourcescurl -X GET "https://console.platform.deutschecloud.app/monitoring/api/resources" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_monitoring_metrics_resources.