Skip to content

List the operations seen in the project's traces, with span counts.

GET
/v1/projects/{projectId}/observability/traces/operations
Code sample: Shell / cURL
curl --request GET \
--url https://stratum.example.com/v1/projects/example/observability/traces/operations \
--header 'Authorization: Bearer <token>'

The operation catalog of the trace search: one item per service and operation in the window, counted over the same spans the search finds (the project’s own spans and the control plane’s spans of requests made against the project). HTTP operations come back as their route template (GET /v1/projects/{projectId}/compute/instances/{instanceId}): the control plane names its server spans that way and sets http.route; older spans named by their raw path are folded into the same template. Pass an item’s operation in operations[] of the search.

Counts are taken from up to 1000 traces in the window; truncated says the window held more.

projectId
required
string
/^p-[a-z0-9-]+$/
service
string

Only this service (resource.service.name).

instanceId
string

An instance id (i-…) or instance ARN of this project: only the spans of requests that acted on it. Anything else is a 400 UNSUPPORTED_RESOURCE.

start
string format: date-time

Window start (RFC 3339). Default end minus one hour.

end
string format: date-time

Window end (RFC 3339). Default now.

The operations, most spans first.

Media typeapplication/json
object
items
required
Array<object>

One operation of the trace operation catalog.

object
service
required

The emitting service (resource.service.name).

string
operation
required

<METHOD> <route> for an HTTP operation, else the span name. The value operations[] of the trace search takes.

string
method

HTTP method; absent for a non-HTTP operation.

string
route

Route template (http.route); absent for a non-HTTP operation.

string
count
required

Spans of this operation counted in the window.

integer format: int64
truncated
required

The window held more traces than were counted (1000): counts are a sample and a rare operation may be missing.

boolean

Example

{
"items": [
{
"operation": "GET /v1/projects/{projectId}/compute/instances/{instanceId}",
"route": "/v1/projects/{projectId}/compute/instances/{instanceId}"
}
]
}

Bad request.

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example

{
"issues": [
{
"code": "ACTION_NOT_APPLICABLE",
"action": "compute:CreateVpc"
}
]
}

Upstream temporarily unavailable (driver / scheduler / dependency).

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example

{
"issues": [
{
"code": "ACTION_NOT_APPLICABLE",
"action": "compute:CreateVpc"
}
]
}