Get Retention Policy

GET

/observability/v1/workspaces/{workspace}/engines/{engine}/retention-policies/{id}

curl --request GET \
  --url https://example.com/observability/v1/workspaces/example/engines/example/retention-policies/example

Returns a retention policy by unique id. Use - to look it up regardless of provider.

Parameters

Path Parameters

workspace

required

string

The workspace the retention policy belongs to.

engine

required

string

The provider: qibdo, aws, gcp, or azure, or ’-’ to look up across all providers.

id

required

string

The unique identifier of the retention policy to retrieve.

Responses

200

OK

Media type application/json

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

id

The unique identifier of the retention policy.

stringOutput only

workspace_id

The workspace this policy governs. Derived from the {workspace} path segment on create; reported read-only thereafter.

stringOutput only

location_id

required

Weak reference to a topology Location — where the telemetry resides. Immutable after create.

string

engine

The provider that stores this workspace’s telemetry.

string format: enum Output only

Allowed values: ENGINE_UNSPECIFIED ENGINE_QIBDO ENGINE_AWS ENGINE_GCP ENGINE_AZURE

created

Timestamp when the policy was created.

string format: date-time Output only

updated

Timestamp when the policy was last updated.

string format: date-time Output only

qibdo

Retention windows for a Qibdo-managed workspace.

object

logs_interactive_seconds

required

Interactive log retention window, in seconds (> 0).

string

metrics_interactive_seconds

required

Interactive metric retention window, in seconds (> 0).

string

traces_interactive_seconds

required

Interactive trace retention window, in seconds (> 0).

string

activity_interactive_seconds

required

Interactive activity retention window, in seconds (> 0).

string

Example

{
  "engine": "ENGINE_UNSPECIFIED"
}

default

Default error response

Media type application/json

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

code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32

message

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.

string

details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object

@type

The type of the serialized message.

string

key

additional properties

any

Example ^generated

{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}