Configure Telemetry Relay

You can configure Telemetry Relay using the Cloud Console or the Telemetry Relay API. To configure Telemetry Relay, you define the following:

• Destinations: Where telemetry is sent, such as an HTTPS endpoint.
• Streams: Predefined telemetry categories, such as audit logs.
• Pipelines: A configuration that links a stream to a destination (endpoint).

For information about supported telemetry, see Introduction to Telemetry Relay.

​

Prerequisites

To configure Telemetry Relay or view destinations and pipelines, you need one of the following roles: To manage Telemetry Relay through the API, see the Telemetry Relay API reference.

​

Create a destination

Create a destination using the Cloud Console:

1. Navigate to Telemetry Relay in the Cloud Console and select Destinations.
2. Click Create destination.
3. On the Create destination page, fill in the following fields:
   • Display name: A label for the destination. The display name appears in the Destinations table and in the Destination dropdown when you create a pipeline.
   • Endpoint type: The protocol the destination uses to receive telemetry. Self-service supports HTTPS endpoints only.
   • Endpoint URL: The URL where Telemetry Relay sends telemetry.
   • Authentication type: The credential scheme Telemetry Relay uses when it connects to the endpoint.
4. Click Submit.

The new destination appears in the Destinations table.

​

Create a pipeline

Create a pipeline using the Cloud Console:

1. Navigate to Telemetry Relay in the Cloud Console.
2. Click Create pipeline.
3. On the Create pipeline page, fill in the following fields:
   • Source: The telemetry stream to forward. Streams are predefined categories of CoreWeave telemetry, such as Console Audit Logs or Kubernetes API Audit Logs.
   • Destination: An existing destination to receive the stream. The dropdown lists destinations created in the Destinations tab.
   After you fill in both fields, a read-only Generated Pipeline Name field shows the resulting slug, which combines the source and destination names (for example, logs-audit-console-my-endpoint). You don’t enter a name yourself.
4. Click Submit.

The new pipeline appears in the Pipelines table. To leave the Create pipeline page without saving, click Back to Pipelines.

​

List destinations

To view destinations in the Cloud Console, navigate to Telemetry Relay and select Destinations. The table lists each destination’s Name, Type, Region, and Endpoint.

​

List streams

To view available telemetry streams:

1. Navigate to Telemetry Relay and select Create pipeline.
2. Select Source to view the available streams.

Streams appear by display name (for example, Console Audit Logs, Kubernetes API Audit Logs). These are the same streams the Telemetry Relay API exposes through slug identifiers like logs-audit-console. To leave the Create pipeline page without creating a pipeline, click Back to Pipelines. The Source dropdown lists every telemetry stream available to your organization, including streams that are outside the self-service scope. Self-service supports forwarding audit-log streams to HTTPS endpoints. To forward other streams, contact Support.

​

List pipelines

Navigate to Telemetry Relay in the Cloud Console. The Pipelines tab is the default landing view. Each row shows the auto-generated pipeline name, source stream, and destination.

​

Advanced configuration

For other destination types and telemetry streams that are not supported through self-service, contact Support. Examples of custom capabilities that Support can enable:

• Destinations including CoreWeave AI Object Storage buckets (for logs) and Prometheus Remote Write v1 compatible endpoints (for metrics).
• Forwarding for streams outside the self-service scope, such as Kubernetes events, system journal logs, customer cluster metrics, and platform metrics.