List Activities
const url = 'https://example.com/observability/v1/activities';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/observability/v1/activitiesReturns a page of activity records filtered by AIP-160 expression and ordered per AIP-132.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”The maximum number of activities to return. The service may return fewer than this value. If unspecified, at most 20 activities will be returned. The maximum value is 100; values above 100 will be coerced to 100.
A page token, received from a previous ListActivities call.
AIP-160 filter expression.
AIP-132 order_by expression.
Responses
Section titled “ Responses ”OK
ListActivitiesResponse
Response message for ListActivities.
Note: This API intentionally omits total_size from list responses.
Keyset pagination does not support efficient total count computation
(COUNT(*) requires a full table scan). Per AIP-158, total_size is optional.
object
The list of activities.
ActivityRecord
A read-only audit projection of a single platform activity. Each record is derived from the operation that produced it; it is addressed by its own id (and its source operation id), and carries no engine axis.
object
The unique identifier of the activity record.
The identifier of the operation that produced this activity.
The identifier of the actor (principal) that performed the activity.
The type of resource the activity acted upon.
The action performed.
The workspace the activity is scoped to.
The distributed trace identifier correlating this activity.
When the activity occurred.
The opaque JSON audit snapshot captured for this activity.
When the record was created.
A token, which can be sent as page_token to retrieve the next page.
If this field is empty, there are no subsequent pages.
Example generated
{ "activities": [ {} ], "next_page_token": "example"}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" } ]}