lb.load-balancers.liveLive numbers of an application or dedicated load balancer, from the fleet nodes
application and dedicated types only: per node, its counters for this load balancer (connections, requests, 429s, 421s, handshakes, statuses, bytes) and every target’s health as the node checks it, with when the node reported. The active node serves the traffic; the standby’s numbers are its own.
Request syntax
GET /lb/api/load-balancers/{id}/livePath parameters
idRequiredstring
Constraints: uuid
Response
200 with { fleet, nodes }: `fleet` (region, ipv4, ipv6; null before it is placed) and per node: name, active, state, reportedAt, documentVersion, counters (null before its first report), waf (its web ACL’s counters, or null) and targets (each with pool, targetGroup and the node’s view of its health). 400 on lb11/lb21/lb31.
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 lb:DescribeLoadBalancers 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 lb load-balancers live idcurl -X GET "https://console.platform-development.deutschecloud.app/lb/api/load-balancers/id/live" \
-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_lb_load-balancers_live.