Skip to main content

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.

CoreWeave captures and stores metrics and logs to help you monitor the health of your systems and troubleshoot issues. CoreWeave stores logs and metrics in the location where they were generated. For example, the metrics and logs for a cluster in the Availability Zone US-EAST-04A are stored in the US-EAST Super Region. For more information about Regions and Availability Zones, see About Regions and Availability Zones.

Data locations and querying

CoreWeave provides two main locations to query data from:
  • Global location. A single data source for all logs and metrics in all locations, making it easy to query and visualize metrics and logs data across clusters from multiple geographical locations.
  • Super Regional location.The Super Regional data source for your metrics and logs. Super Regional locations are useful for highly latency-sensitive use cases and for issues that require deeper investigation. Super Regional-bound queries return more data because they don’t reach the limits sometimes imposed by global queries.
Use the following table to help determine when to use Global or Super Regional data:
Data sourceWhen to use
GlobalBuilding dashboards spanning multiple regions.
Investigating issues affecting multiple clusters.
Performing high-level observability analysis.
Super RegionalTroubleshooting a specific cluster.
Running large or detailed log queries.
Investigating incidents where query result limits may apply.
For more information about Super Regions, see CoreWeave’s geographical hierarchy.

Metrics data locations

CoreWeave provides the following data sources for metrics:
LocationAddressGrafana data source nameDefault data source
Globalobserve.coreweave.comCoreWeave MetricsYes
US Eastobserve.us-east.coreweave.comCoreWeave Metrics US EastNo
US Westobserve.us-west.coreweave.comCoreWeave Metrics US WestNo
EU Southobserve.eu-south.coreweave.comCoreWeave Metrics EU SouthNo

Logs data locations

Logs are available from both Global and Super Regional data sources. Audit logs are available through dedicated audit logs data sources in each Super Region. In the Global data source, audit logs are also included in the CoreWeave logs dataset to support cross-region observability queries. For more targeted investigation or security analysis, use the regional CoreWeave audit logs data sources. If you don’t find logs in super region, go to the legacy endpoint. Note that some class of logs expire after two weeks. At this time, the location-specific log sources contain all logs except CKS audit logs, and the location-specific audit log data sources only contain CKS audit logs. CoreWeave provides the following data sources for application and audit logs:
LocationAddressesGrafana data source nameDefault data source
Globalobserve.coreweave.comCoreWeave Logs (includes audit logs)Yes
US Eastobserve.us-east.coreweave.com

observe-audit.us-east.coreweave.com
CoreWeave Logs US East

CoreWeave Logs Audit US East
No


No
US Westobserve.us-west.coreweave.com

observe-audit.us-west.coreweave.com
CoreWeave Logs US West

CoreWeave Logs Audit US West
No


No
EU Southobserve.eu-south.coreweave.com

observe-audit.eu-south.coreweave.com
CoreWeave Logs EU South

CoreWeave Logs Audit EU South
No


No
Legacy logs If you can’t find logs in a Super Region endpoint, use the observe-legacy.coreweave.com endpoint. It is a temporary endpoint to allow you to find logs that might not yet be in a Super Region. Note that certain types of logs expire after two weeks, meaning they won’t be available in a Super Region or the legacy endpoint.
LocationAddressesGrafana data source nameDefault data source
Globalobserve-legacy.coreweave.comCoreWeave Logs (Legacy) (includes audit logs)No
Currently, CoreWeave audit logs only contain CKS audit logs. For more information, see the Log content table below.

Log content

Log typeContents
Application and platform logsCustomer workload and pod logs from CKS (for example, container stdout and stderr and application output).
CKS audit logsTracking and recording system events and user activities for security analysis and compliance.
The Global location provides a single unified query interface across all locations and types of logs.

Querying latency

Latency is already low when querying metrics and logs from the Global location. However, for extremely low latency, query from the location the metrics or logs are being stored. To find where the metrics or logs are being stored, use the Cloud Console or API to get the location of your clusters, and then refer to the following table to discover where your cluster’s metrics or logs are stored:
Metrics and logs locationCluster locations
US EastAll clusters in the US-East and CA-East super-regions
US WestAll clusters in the US-West and US-Central super-regions
EU SouthAll clusters in the EU
Last modified on March 30, 2026