List Retention Policies
const url = 'https://example.com/observability/v1/workspaces/example/engines/example/retention-policies';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/workspaces/example/engines/example/retention-policiesReturns a paginated list of retention policies. A specific provider filters to that
provider; - lists across all providers.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The workspace whose retention policies to list.
The provider: qibdo, aws, gcp, or azure, or ’-’ to list across all providers.
Query Parameters
Section titled “Query Parameters ”The maximum number of policies to return. The service may return fewer than this value. If unspecified, at most 20 items will be returned. The maximum value is 100; values above 100 will be coerced to 100.
A page token from a previous ListRetentionPolicies call.
AIP-160 filter expression.
AIP-132 order_by expression, e.g. ‘created desc’.
Responses
Section titled “ Responses ”OK
ListRetentionPoliciesResponse
Response for ListRetentionPolicies. Keyset pagination intentionally omits total_size (AIP-158).
object
The list of retention policies.
A retention policy governs how long telemetry is kept for a workspace, per signal
pillar (logs, metrics, traces, activity). One policy exists per workspace. The
provider that stores the telemetry is reported by the read-only engine field.
object
The unique identifier of the retention policy.
The workspace this policy governs. Derived from the {workspace} path segment on create;
reported read-only thereafter.
Weak reference to a topology Location — where the telemetry resides. Immutable after create.
The provider that stores this workspace’s telemetry.
Timestamp when the policy was created.
Timestamp when the policy was last updated.
Retention windows for a Qibdo-managed workspace.
object
Interactive log retention window, in seconds (> 0).
Interactive metric retention window, in seconds (> 0).
Interactive trace retention window, in seconds (> 0).
Interactive activity retention window, in seconds (> 0).
A token to retrieve the next page; empty when there are no further pages.
Example
{ "retention_policies": [ { "engine": "ENGINE_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" } ]}