List Stat Descriptors
const url = 'https://example.com/storage/v1/workspaces/example/statDescriptors';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/storage/v1/workspaces/example/statDescriptorsReturns the static UI metadata (code, display name, unit, description) for every stat in
BucketAggregateStats, so the console renders labels and units without hardcoding them. The
registry is version-bound and engine-neutral; workspace scopes authorization only.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The workspace the caller is authorized in
Responses
Section titled “ Responses ”OK
List Stat Descriptors Response
The full static descriptor registry — one descriptor per stat in BucketAggregateStats.
object
The stat descriptors, one per BucketAggregateStats stat field.
Stat Descriptor
Static UI metadata for one stat in BucketAggregateStats: the label and unit the console renders for that stat’s KPI card, keyed by the stat’s field name. Served by ListStatDescriptors so the UI never hardcodes labels or units.
object
The stat’s field name in BucketAggregateStats (for example, “total_size_bytes”).
The human-facing card label (for example, “Total Stored”).
The unit the stat’s value is expressed in.
A short description of what the stat measures.
Example
{ "stat_descriptors": [ { "unit": "STAT_UNIT_UNSPECIFIED" } ]}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}