> ## 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. # Introduction to Telemetry Relay > Use Telemetry Relay to forward telemetry to destinations outside of CoreWeave Telemetry Relay is a fully-managed solution for forwarding telemetry to destinations outside of CoreWeave's observability platform. Telemetry Relay has the following features and benefits: * **Comprehensive data aggregation**: Ingests telemetry data from multiple sources. * **Flexible routing**: Fine-grained data routed to customer-specified endpoints. * **Guaranteed delivery**: Prioritizes data completeness with minimal latency. * **Fully managed with easy configuration**: Zero-operational overhead for configuring data filters and endpoint routing. By supporting multiple data streams to a variety of destination endpoints, Telemetry Relay provides flexibility for managing and analyzing your data. Architecture diagram for Telemetry Relay. * **Streams**: Pre-defined telemetry categories: for example, audit logs. * **Pipelines**: A configuration that links a stream to an endpoint. * **Endpoints**: Destinations, such as HTTPS endpoints. ## Configure Telemetry Relay To set up and configure Telemetry Relay, contact [Support](/support). By default, Telemetry Relay forwards audit logs to HTTPS endpoints. Audit logs include CKS audit logs, CoreWeave API audit logs, Console audit logs, and [Support Access Management](/security/support-access-management) logs for customers who enable Support Access Management. Support can also help you assess feasibility and timelines for other advanced configurations, including: * **Data streams**: Platform logs and platform metrics, in addition to audit logs. * **Forwarding and filtering**: Routing and filtering rules for what gets sent. * **Destination endpoints**: CoreWeave AI Object Storage and Prometheus Remote Write v1, in addition to HTTPS endpoints. * **Advanced networking requirements**