> ## Documentation Index > Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt > Use this file to discover all available pages before exploring further. # Get telemetry stream > Returns a single telemetry stream by its `ref.slug`. Includes the stream's `spec` (display name, kind, label-selector filter) and `status` (current state and active zones). ## OpenAPI ````yaml /openapi/o11y/openapi.yaml get /v1beta1/telemetryrelay/streams/{ref.slug} openapi: 3.0.3 info: title: CoreWeave Telemetry Relay API version: 0.0.1 description: >- The CoreWeave Telemetry Relay API provides programmatic control over Telemetry Relay, CoreWeave's managed solution for forwarding audit logs over HTTPS to destinations outside the CoreWeave observability platform. servers: - url: https://api.coreweave.com security: - bearerAuth: [] tags: - name: TelemetryRelayService description: >- Endpoints for managing forwarding endpoints, forwarding pipelines, and reading available telemetry streams. Use these endpoints to configure how CoreWeave platform telemetry is forwarded to destinations outside the CoreWeave observability platform. For Cloud Console procedures, see the [Telemetry Relay configure guide](/observability/telemetry-forwarding/configure). Self-service is limited to forwarding audit logs to HTTPS endpoints. To forward other telemetry or use other destination types, [contact Support](/support). Your organization must be enabled for self-service before you can create destinations or pipelines: write requests from an organization that is not enabled return `404` with reason `TELEMETRYRELAY_ORGANIZATION_NOT_FOUND`. [Contact Support](/support) to request enablement. Write operations (`POST`, `PATCH`, `DELETE`) require the `Telemetry Relay Admin` role; read operations (`GET`) require the `Telemetry Relay Reader` role. paths: /v1beta1/telemetryrelay/streams/{ref.slug}: get: tags: - TelemetryRelayService summary: Get telemetry stream description: >- Returns a single telemetry stream by its `ref.slug`. Includes the stream's `spec` (display name, kind, label-selector filter) and `status` (current state and active zones). operationId: TelemetryRelayService_GetStream parameters: - name: ref.slug in: path required: true schema: type: string responses: '200': description: OK content: application/json: schema: $ref: >- #/components/schemas/coreweave.telemetryrelay.svc.cluster.v1beta1.GetStreamResponse default: description: Default error response content: application/json: schema: $ref: '#/components/schemas/google.rpc.Status' components: schemas: coreweave.telemetryrelay.svc.cluster.v1beta1.GetStreamResponse: type: object properties: stream: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.TelemetryStream google.rpc.Status: description: >- 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](https://github.com/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](https://cloud.google.com/apis/design/errors). type: object properties: code: description: >- The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code]. type: integer format: int32 message: description: >- 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. type: string details: description: >- A list of messages that carry the error details. There is a common set of message types for APIs to use. type: array items: $ref: '#/components/schemas/google.protobuf.Any' coreweave.telemetryrelay.types.v1beta1.TelemetryStream: type: object properties: ref: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.TelemetryStreamRef spec: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.TelemetryStreamSpec status: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.TelemetryStreamStatus google.protobuf.Any: description: >- Contains an arbitrary serialized message along with a @type that describes the type of the serialized message. type: object properties: '@type': description: The type of the serialized message. type: string additionalProperties: true coreweave.telemetryrelay.types.v1beta1.TelemetryStreamRef: type: object properties: slug: type: string maxLength: 32 minLength: 3 pattern: ^[a-zA-Z0-9][a-zA-Z0-9-]+$ coreweave.telemetryrelay.types.v1beta1.TelemetryStreamSpec: description: >- Configuration for a telemetry stream. `displayName` is a human-readable label; `filter` narrows the stream by label selectors; `kind` declares the category of telemetry the stream carries. type: object properties: displayName: type: string filter: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.LabelSelector kind: description: >- Category of telemetry carried by the stream. Self-service forwards audit logs, so `LOGS` is the only available kind. Required. type: string enum: - STREAM_KIND_LOGS coreweave.telemetryrelay.types.v1beta1.TelemetryStreamStatus: type: object properties: createdAt: type: string format: date-time updatedAt: type: string format: date-time stateMessage: type: string zonesActive: type: array items: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.TelemetryStreamStatus_ZoneClusterStatus state: description: >- Current state of the stream. `ACTIVE` when data is being collected, `INACTIVE` when collection is paused, `ERROR` if collection has failed. type: string enum: - TELEMETRY_STREAM_STATE_ACTIVE - TELEMETRY_STREAM_STATE_ERROR - TELEMETRY_STREAM_STATE_INACTIVE readOnly: true coreweave.telemetryrelay.types.v1beta1.LabelSelector: type: object properties: include: type: object additionalProperties: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.StringList exclude: type: object additionalProperties: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.StringList coreweave.telemetryrelay.types.v1beta1.TelemetryStreamStatus_ZoneClusterStatus: type: object properties: zoneSlug: type: string clusters: type: array items: $ref: >- #/components/schemas/coreweave.telemetryrelay.types.v1beta1.TelemetryStreamStatus_ClusterStatus coreweave.telemetryrelay.types.v1beta1.StringList: type: object properties: values: type: array items: type: string coreweave.telemetryrelay.types.v1beta1.TelemetryStreamStatus_ClusterStatus: type: object properties: id: type: string securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: CoreWeave API access token sent as a bearer token. x-default: Bearer [CW-API-TOKEN] ````