> ## 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.
# Query logs and metrics
> Call the metrics and logs HTTP APIs with a CoreWeave access token, including regional hosts and legacy endpoints
Programmatic access to metrics and logs lets you integrate CoreWeave observability data into custom dashboards, alerting pipelines, and automation workflows. Query the Prometheus-compatible and Loki-compatible HTTP APIs directly when you need capabilities beyond what [CoreWeave Grafana](/observability/managed-grafana) or [self-hosted Grafana](/observability/self-hosted-grafana) provide.
To efficiently export metrics and logs at scale, consider setting up telemetry forwarding to an external system with [CoreWeave Telemetry Relay](/observability/telemetry-forwarding/relay).
For more information about metric and log data sources, see [Data sources](/observability/logs-metrics/data-sources).
## Authentication and access
Use a [CoreWeave API access token](/security/authn-authz/manage-api-access-tokens) for HTTP requests to the observability query endpoints. Pass the token in the `Authorization` header as a Bearer token.
Replace **`[API-ACCESS-TOKEN]`** in the following examples with your API access token secret from the [Access Tokens](https://console.coreweave.com/tokens) page in the Cloud Console.
CoreWeave evaluates authorization for observability data through [IAM Access Policies](/security/iam/access-policies). For read-only access to metrics and logs through the APIs and CoreWeave Grafana, principals typically need the **Observability Viewer** role. In the legacy group-based model, membership in the `metrics` group granted equivalent access. See [Legacy User Permissions](/security/iam/access-policies/legacy-permissions) for details.
The secret for a [CoreWeave API access token](/security/authn-authz/manage-api-access-tokens) is the same value whether you pass it in `Authorization` headers or embed it in a [kubeconfig](/security/authn-authz/manage-api-access-tokens) as `users[].user.token` for `kubectl`. The difference is which service you call: use observability hostnames such as `observe.coreweave.com` for metrics and logs APIs, and use your cluster Kubernetes API server URL from the kubeconfig for the Kubernetes API.
## Query metrics
You can query metrics through the Prometheus-compatible HTTP API. The following sections describe the available endpoints, the supported request paths, and example queries for both instant and range data.
### Global and Super Regional endpoints
Metrics are available from the Global hostname and from Super Regional hostnames. The endpoint you choose affects both query performance and the completeness of results. Super Regional endpoints can return more complete results for large or detailed queries and offer lower latency when your data is stored in that Super Region. For the authoritative list of metrics hostnames, see [Metrics data locations](/observability/logs-metrics/data-sources#metrics-data-locations) on the Data sources page.
The following examples use the Global hostname `observe.coreweave.com`. To send the same request to a Super Regional endpoint, swap the hostname and keep the path (for example, `https://observe.us-east.coreweave.com/api/v1/query`).
The following paths are supported:
| Supported paths |
| ----------------------------------- |
| `/api/v1/query` |
| `/api/v1/labels` |
| `/api/v1/query_range` |
| `/api/v1/series` |
| `/api/v1/label//values` |
| `/api/v1/query_exemplars` |
| `/api/v1/metadata` |
| `/api/v1/rules` |
#### Instant metric query
The following example uses `curl` to run an instant query that returns the total time GPUs spent in idle mode (in seconds):
```bash theme={"system"}
curl -G "https://observe.coreweave.com/api/v1/query" \
-H "Authorization: Bearer [API-ACCESS-TOKEN]" \
--data-urlencode 'query=node_gpu_seconds_total{mode="idle"}'
```
#### Range metric query
For a time range, use `query_range` with `start`, `end`, and `step` as Unix timestamps in seconds:
```bash theme={"system"}
curl -G "https://observe.coreweave.com/api/v1/query_range" \
-H "Authorization: Bearer [API-ACCESS-TOKEN]" \
--data-urlencode 'query=node_gpu_seconds_total{mode="idle"}' \
--data-urlencode 'start=[START-TIMESTAMP]' \
--data-urlencode 'end=[END-TIMESTAMP]' \
--data-urlencode 'step=60'
```
Replace **`[START-TIMESTAMP]`** and **`[END-TIMESTAMP]`** with the range you need.
For more information about querying Prometheus metrics, see the Prometheus [HTTP API documentation](https://prometheus.io/docs/prometheus/latest/querying/api/).
CoreWeave does not support the [Prometheus Federation API](https://prometheus.io/docs/prometheus/latest/federation/).
### Legacy metrics
If your queries cover dates before the October 2024 backend migration, query the Legacy Prometheus host to retrieve that historical data. CoreWeave migrated its metrics backend in October 2024, and the new backend reliably contains data from **October 21, 2024** onward. For metrics collected before that date, query the Legacy Prometheus host in addition to the preceding primary endpoints. The Legacy service exposes the same Prometheus HTTP API paths (for example, `/api/v1/query` and `/api/v1/query_range`).
| Host | Use |
| -------------------------------------- | --------------------------------------------------------- |
| `prometheus-legacy.ord1.coreweave.com` | Historical metrics data collected before October 21, 2024 |
Query the current endpoint first (for example, `observe.coreweave.com`), because it's faster. If the result has gaps for dates before October 21, 2024, run the same PromQL query against `https://prometheus-legacy.ord1.coreweave.com` with the same `Authorization: Bearer [API-ACCESS-TOKEN]` header.
## Query logs
You can query logs through the Loki-compatible HTTP API. The following sections cover the host matrix for each log type, the supported paths, and an example query.
### Global, Super Regional, and legacy log endpoints
At the Global host, application, platform, and audit logs share one Loki-compatible API. In Super Regions, application and platform logs use `observe..coreweave.com`, and **CKS audit logs** use the dedicated audit host `observe-audit..coreweave.com` in that Super Region. For the full matrix and Grafana data source names, see [Logs data locations](/observability/logs-metrics/data-sources#logs-data-locations). Some log types expire after two weeks.
| Location | Application and platform logs | CKS audit logs |
| --------------- | -------------------------------- | --------------------------------------------------------------------- |
| Global | `observe.coreweave.com` | `observe.coreweave.com` (audit logs are included in the same dataset) |
| US East | `observe.us-east.coreweave.com` | `observe-audit.us-east.coreweave.com` |
| US West | `observe.us-west.coreweave.com` | `observe-audit.us-west.coreweave.com` |
| EU South | `observe.eu-south.coreweave.com` | `observe-audit.eu-south.coreweave.com` |
| Legacy (Global) | `observe-legacy.coreweave.com` | `observe-legacy.coreweave.com` (includes audit logs) |
The following paths are supported:
| Supported paths |
| ---------------------------------- |
| `/loki/api/v1/query` |
| `/loki/api/v1/query_range` |
| `/loki/api/v1/labels` |
| `/loki/api/v1/label//values` |
| `/loki/api/v1/series` |
| `/loki/api/v1/index/stats` |
| `/loki/api/v1/index/volume` |
| `/loki/api/v1/index/volume_range` |
| `/loki/api/v1/format_query` |
#### Log query format
The following example returns Kubernetes audit logs for a cluster:
```bash theme={"system"}
curl -G "https://observe.coreweave.com/loki/api/v1/query_range" \
-H "Authorization: Bearer [API-ACCESS-TOKEN]" \
--data-urlencode 'query={logging_component="unicaster", app="kube-apiserver", stream="", cluster="[CLUSTER-NAME]"} | json | apiVersion="audit.k8s.io/v1" | json sourceIPs="sourceIPs" | json user_groups="user.groups"'
```
Replace `[CLUSTER-NAME]` with your cluster name.
### Legacy logs
In March 2025, CoreWeave introduced Super Regional log endpoints. If you need logs collected before that date, query the Legacy logs endpoint in addition to the preceding primary endpoints. The Legacy service exposes the same Loki API paths (for example, `/loki/api/v1/query` and `/loki/api/v1/query_range`).
| Host | Use |
| ------------------------------ | ---------------------------------------------------------------------------- |
| `observe-legacy.coreweave.com` | Historical log data collected before the March 2025 Super Regional migration |
For background, see [Legacy logs](/observability/logs-metrics/data-sources#logs-data-locations) on the Data sources page.
## Grafana Explore
If you prefer an interactive UI to direct API calls, you can run the same kinds of ad hoc queries in Grafana. **[Grafana Explore](https://grafana.com/docs/grafana/latest/visualizations/explore/)** is available in CoreWeave Grafana and supports the full range of PromQL and LogQL for ad hoc queries on metrics and logs. You can also view metadata such as which metrics are available or which labels you can use to filter PromQL queries.
CoreWeave's default dashboards offer curated views of specific logs and metrics, and you can use the **Explore** tab to investigate metrics in more detail.
For more information, see [Get started with Grafana Explore](https://grafana.com/docs/grafana/latest/visualizations/explore/get-started-with-explore/).