Grafana
Use managed Grafana, or build custom dashboards with a self-hosted instance
CoreWeave provides a managed Grafana instance to view predefined dashboards with compute and storage summaries, and detailed reports of the GPUs, CPUs, memory, and network activity for each Pod.
To access the managed Grafana instance, use the menu in the Account Details section of CoreWeave Cloud or navigate directly to https://grafana.coreweave.com.

Grafana menu
In this Grafana instance, the dashboards cannot be cannot modified, or new ones created. For complete control, deploy a own self-hosted Grafana instance on CoreWeave Cloud.
To build custom dashboards from CoreWeave's Prometheus metrics, deploy a Grafana instance with CoreWeave Apps.

Grafana
- 1.
- 2.Search for Grafana, then click it to access the deployment screen.
- 3.Click Deploy in the upper-right corner.
- 4.Give it a meaningful name.
- 5.In most cases, leave Expose to the Public via Ingress selected.
- 6.Click Deploy.
Wait for the Pods to deploy, then click the Ingress URL to log in with the username and password in the upper-right corner.

Deployment screen
Our Prometheus scraping service offers many useful billing metrics for use in self-hosted Grafana instances. For an on-premise Grafana instance, follow these same steps to connect to CoreWeave's Prometheus service.
- 1.In the Grafana instance, go to Configuration -> Data Sources in the lower left menu.Data sources menu
- 2.Click Add New Datasource and select Prometheus.
- 3.Set the Name to CoreWeave.
- 4.Set the URL to
https://prometheus.ord1.coreweave.com
. - 5.Click Add Header in the Custom HTTP Headers section.
- 6.Set the following values for Custom HTTP Header. Header:
Authorization
Value:Bearer [my-token]
Replace[my-token]
with the API Access token.Connection settings - 7.Click Save & Test at the bottom of the page to verify and save the new datasource.Successful connection
If Kubernetes is already configured, the token is in the
users
section of kubeconfig
. If not, generate a new one on the API Access page.To view the unredacted
kubeconfig
, use kubectl
.kubectl config view --raw
Here's a redacted example:
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: DATA+OMITTED
server: https://k8s.ord1.coreweave.com
name: coreweave
contexts:
- context:
cluster: coreweave
namespace: tenant-EXAMPLE
user: token-EXAMPLE-USER
name: coreweave
current-context: coreweave
kind: Config
preferences: {}
users:
- name: token-EXAMPLE-USER
user:
token: REDACTED
The API Access token, which is
REDACTED
in this example, is located in the users
section at the bottom.If there is more than one context in the kubeconfig, make sure to choose the token for the desired namespace.
If building a Grafana dashboard for the first time, we suggest reading Build your first dashboard at Grafana Labs.
The Grafana
billing
metrics are in the CoreWeave datasource. There is no need to filter the namespace when adding these metrics to a dashboard.
Billing metrics
There's no need to filter the
namespace
label to the namespace for any metric. It will be automatically inserted on all queries received.Last modified 19d ago