# Resource Overview

The `ace get-all` command provides a dashboard view of all provisioned resources in your current project and region -- similar to `kubectl get all` for Kubernetes.

***

## Usage

```bash
ace get-all
```

**Aliases:** `all`, `status`

***

## Example Output

```
-- Instances (2) --
  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx  my-server                 ACTIVE       ACE.CPU.4C16R
  yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyy  web-server                ACTIVE       ACE.CPU.2C4R

-- Volumes (3) --
  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx  boot-vol                  in-use       100GB
  yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyy  data-vol                  available    50GB
  zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzz  db-storage                in-use       200GB

-- VPCs (1) --
  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx  my-vpc                    ACTIVE       shared=false  subnets=1

-- Routers (1) --
  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx  my-router                 ACTIVE       gw=ext-net-id...

-- Security Groups (2) --
  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx  default                   4 rules
  yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyy  web-sg                    8 rules

-- Floating IPs (1) --
  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx  203.0.113.10              ACTIVE       fixed=10.0.0.5

-- Key Pairs (1) --
  my-keypair                          ssh        SHA256:abc...

-- Load Balancers (0) --
  (none)

-- Snapshots (1) --
  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx  snap-data-vol             available    50GB

-- Deployments (CaaS) (1) --
  my-app                              shared     Running      nginx:latest              replicas=2

-- K8s Clusters (1) --
  c-m-abc123           my-cluster                active       v1.32.6

-- Total: 13 resources --
```

***

## Resource Categories

The command fetches the following resource types in parallel:

| Category           | API Source            |
| ------------------ | --------------------- |
| Instances          | `ListInstances`       |
| Volumes            | `ListVolumes`         |
| VPCs               | `ListVPCs`            |
| Routers            | `ListRouters`         |
| Security Groups    | `ListSecurityGroups`  |
| Floating IPs       | `ListFloatingIPs`     |
| Key Pairs          | `ListKeyPairs`        |
| Load Balancers     | `ListLoadBalancers`   |
| Snapshots          | `ListSnapshots`       |
| Deployments (CaaS) | `ListCaasDeployments` |
| K8s Clusters       | `ListK8sClusters`     |

***

## Concurrency and Retries

All resource types are fetched concurrently for speed. The backend can sometimes return errors under heavy concurrent load, so **Volumes** and **Snapshots** include an automatic retry with a 500ms delay if the first request fails.

If a resource type fails to load, it is shown with an error indicator:

```
-- Volumes (error) --
  Warning: connection timeout
```

***

## JSON Output

Get all resources as a structured JSON array:

```bash
ace get-all -o json
```

The JSON output is an array of objects, each with `resource`, `data`, and optionally `error` fields:

```json
[
  {
    "resource": "instances",
    "data": { ... }
  },
  {
    "resource": "volumes",
    "data": { ... }
  },
  {
    "resource": "snapshots",
    "error": "connection timeout"
  }
]
```

***

## Global Flags

| Flag           | Description                                |
| -------------- | ------------------------------------------ |
| `-o, --output` | Output format: `table` (default) or `json` |
| `--project`    | Override project ID                        |
| `--region`     | Override region                            |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.acecloud.ai/knowledge-base/cli/monitoring/resource-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.