Logs
sf logs service=checkout level>=warn since=15mStructured at ingest and indexed by every key. Nothing is sampled, nothing is dropped, nothing is "rehydrated" later.
// ingesting 12,408 spans/s · p99 41 ms · 0 dropped
// 14-day trial · no card · otlp native
signals
Logs, metrics, traces and profiles land in the same store with the same schema, so one line of SFQL answers the question you actually have — not the four questions your four tools can answer.
sf logs service=checkout level>=warn since=15mStructured at ingest and indexed by every key. Nothing is sampled, nothing is dropped, nothing is "rehydrated" later.
sf rate(http.errors) by route | top 5Native histograms with exemplars, each one linked to the exact trace that produced the outlier.
sf trace where duration>2s and db.calls>40Full-fidelity spans kept for 30 days. Tail-based retention decides what matters after the request finished, not before.
incident
The frame that cost you 1.4 seconds is highlighted before you ask. Click it and Stackframe shows the query plan, the connection-pool wait and the deploy that changed the index.
pricing
$0.18per GB ingested