List the operations seen in the project's traces, with span counts.
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.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Only this service (resource.service.name).
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.
Window start (RFC 3339). Default end minus one hour.
Window end (RFC 3339). Default now.
Responses
Section titled “Responses”The operations, most spans first.
object
One operation of the trace operation catalog.
object
The emitting service (resource.service.name).
<METHOD> <route> for an HTTP operation, else the span name. The
value operations[] of the trace search takes.
HTTP method; absent for a non-HTTP operation.
Route template (http.route); absent for a non-HTTP operation.
Spans of this operation counted in the window.
The window held more traces than were counted (1000): counts are a sample and a rare operation may be missing.
Example
{ "items": [ { "operation": "GET /v1/projects/{projectId}/compute/instances/{instanceId}", "route": "/v1/projects/{projectId}/compute/instances/{instanceId}" } ]}Bad request.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
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.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
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
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}Upstream temporarily unavailable (driver / scheduler / dependency).
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
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.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
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
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}