Configure Telemetry Relay
Learn how to configure Telemetry Relay
CoreWeave supports forwarding telemetry data to external systems.
To set up and configure Telemetry Relay, contact Support in order to define the following:
- Data streams
- Forwarding and filtering requirements
- Destination endpoints
CKS telemetry forwarding requirements
To forward CKS metrics to an external system, you will need to deploy the Prometheus Agent inside your CKS cluster and configure it to use remote-write.
CKS Clusters deployed before July 7, 2025 have Prometheus Operator pre-installed.
CKS clusters deployed after July 7, 2025 do not have the Prometheus Operator pre-installed. Clusters deployed after this date must install Prometheus Operator before proceeding with the steps below.
To deploy the Prometheus Agent in your CKS cluster, complete the following steps:
-
Choose a namespace to deploy the Prometheus Agent in. You may deploy the Prometheus Agent to an existing namespace, or create a new namespace with
kubectl:To create a new namespace, run the following command, replacing
MY_REMOTE_WRITE_NAMESPACEwith your chosen namespace:Example$kubectl create namespace MY_REMOTE_WRITE_NAMESPACE -
Configure the Prometheus Agent CustomResource YAML file with your remote-write destination, as in the following example:
sample-prometheus-agent.yamlapiVersion: monitoring.coreos.com/v1alpha1kind: PrometheusAgentmetadata:name: my-prom-agentnamespace: MY_REMOTE_WRITE_NAMESPACEspec:remoteWrite:- url: "https://example-url/api/v1/write"...For more details on specifying the
remoteWriteconfiguration(s), see Prometheus Operator's API reference. -
Use
kubectlto deploy the Prometheus Agent to your CKS cluster with the following command, replacingsample-prometheus-agent.yamlwith the appropriate filename:Example$kubectl apply -f sample-prometheus-agent.yamlMetrics generated within your CKS cluster will now remote-write to your specified destination.