Captured sessions
A captured session is a session whose detail is kept by sampling: its spans, logs and screens. Users are not metered. Crashes, errors and the session summaries behind release health are sent from every session, captured or not. On Solo, only the detail stops at the cap: crashes and summaries keep flowing, and there is never an overage. On Pro, sessions above the included 50k are billed per 1,000. To capture fewer sessions, lower the session sampling rate in the remote configuration.Caps and alerts
Each billing period counts captured sessions: the whole 14 days of the trial, then each calendar month on a plan. The console shows the count against your cap, or against the included sessions on Pro without one.- Caps. The trial stops capturing detail at 25k sessions and Solo at 10k. On Pro you can set a spend cap, the most a month may cost; at the sessions it pays for, detail capture stops the same way. Only owners set it, and raising it resumes capture at once. Devices pick the change up at their next policy fetch, so a few more sessions may arrive after the cap; they are never billed beyond it.
- Alerts. Owners and admins get an email at 50%, 80% and 100% of the cap (or of the included sessions), and when a day’s sessions jump to ten times the daily average of the week before.
When the trial ends
At the end of the trial, if no plan was chosen, collection stops: the SDKs get the kill switch and the ingest endpoint answers402. Your data stays readable for 14 days, the
trial’s retention, and choosing a plan resumes ingest at once.
Annual plans and the price lock
- An annual plan costs 10 months for 12, paid up front.
- If you subscribe before general availability, you keep the price you started on for 24 months.