deploy.apps.resource-activityRead one node's last events and, for a container, its last log lines
node is a key from the resources tree, e.g. machine:i-abc or container:i-abc:web. Log lines need monitoring:FilterLogEvents.
Request syntax
GET /deploy/api/apps/{id}/resources/activityPath parameters
idRequiredstring
Constraints: uuid
Query parameters
nodeRequiredstring
Key of a node from the resources tree, e.g. machine:i-abc or container:i-abc:web
Constraints: 1-300 chars
Response
200 with `data`: the `node`, its last 20 `events` (at, level, phase, source, message; oldest first), and for a container its last 100 `logs` lines — null otherwise, with `logsUnavailable` saying why. 404 when the node is not in the caller’s tree.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
nodeAlwaysobject
The node, as the resources tree has itnode.keyAlwaysstring
Unique key, e.g. machine:i-abc or container:i-abc:webnode.parentAlwaysstring, may be null
Key of the parent node; null for the rootnode.kindAlwaysone of app, deployment, load-balancer, machine, container, domain, database, cache, broker
What the node isnode.serviceAlwaysstring
Service it belongs tonode.nameAlwaysstring
Namenode.detailAlwaysstring, may be null
One line: image, size, address or enginenode.hrefAlwaysstring, may be null
Console path of its own page; null if nonenode.healthAlwaysobject
Health and whynode.health.healthAlwaysone of healthy, progressing, degraded, suspended, missing, unknown
Healthnode.health.reasonAlwaysstring
Whynode.syncAlwaysobject, may be null
Sync of a machine or container; null for other nodesnode.sync.syncAlwaysone of in_sync, out_of_sync, unknown
Whether it runs what it shouldnode.sync.reasonAlwaysstring
Whynode.sync.rollingOutAlwaysboolean
Out of sync only because a rollout is in progressnode.reportedAtAlwaysstring, may be null
When it last reported; null if never or not applicablenode.eventsAlwaysarray of object
Where its events are read from (resource-activity reads them)node.events[].resourceTypeAlwaysstring
Kind of resource the events are aboutnode.events[].resourceIdAlwaysstring
Its idnode.logStreamAlwaysstring, may be null
Log stream prefix of a container; null otherwiseeventsAlwaysarray of object
Its last 20 events, oldest firstevents[].atAlwaysstring
Whenevents[].levelAlwaysone of info, warn, error
info, warn or errorevents[].phaseAlwaysstring, may be null
Stage; null if noneevents[].sourceAlwaysone of control_plane, machine
control_plane or machineevents[].messageAlwaysstring
What happenedlogsAlwaysarray of object, may be null
A container’s last 100 log lines, oldest first; null otherwiselogs[].atAlwaysstring
When the line was writtenlogs[].streamAlwaysstring
Log streamlogs[].messageAlwaysstring
The linelogsUnavailableAlwaysstring, may be null
Why logs is null for a container; null otherwise
Checked against the handlers: every route test validates their answers against this schema.
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 deploy:DescribeApp 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 deploy apps resource-activity id --node examplecurl -X GET "https://console.platform-development.deutschecloud.app/deploy/api/apps/id/resources/activity" \
-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_deploy_apps_resource-activity.