Skip to main content
CoreWeave Observe™ sets best-effort service level objectives (SLOs) for the availability, latency, and durability of its observability services, and applies limits to telemetry retention and log line size. This page lists those service levels and limits. Service level objectives are the targets that CoreWeave aims to meet for each service, covering the availability and latency of your queries and the durability of your stored logs and metrics.
These service levels and limits are best-effort product performance guidelines.

Service level objectives

The following table lists the service level objectives for CoreWeave observability services. Availability targets apply to real customer traffic, and query endpoints are reached through observe.coreweave.com.
ServiceSLO measurement
CoreWeave Grafana99.9% of all requests to CoreWeave Grafana complete successfully.
Logs queryAvailability: 99.9% of all requests through observe.coreweave.com complete successfully.
Response latency: 99% of log queries return results within 1 minute.
Retention: 99.999% of audit logs are retained for 3 months. 99.999% of other logs are retained for 7 days.
Metrics queryAvailability: 99.9% of all requests through observe.coreweave.com complete successfully.
Response latency: 99% of metric queries spanning 7 days at a 1-minute step return within 5 seconds.
Retention: 99.999% of metrics are retained for 3 months.
For information about querying logs and metrics through these endpoints, see Query Logs and Metrics.

Retention limits

CoreWeave retains telemetry based on the limits described below. Data older than the retention limit may no longer be queryable.
Telemetry typeRetention limit
Audit logs3 months
Other logs (platform and application logs)7 days
Metrics3 months

Log size limits

Individual log lines are subject to a maximum size. Log lines that exceed the limit may be dropped or truncated.
LimitSize
Log line size limit256 KB
Telemetry Relay log line size limit100 KB
Last modified on June 12, 2026