Overview
Monitoring reports what your API does in production: which requests fail, which are slow, what changed in the release that broke them, and which commit is the likely cause.
Enable monitoring on project and rebuild SDKs to include reporter. Each SDK still ships with logging.enabled off; developer using it enables reporting in application. Browser personal context requires separate setLoggingConsent(true). Nothing is sent before application opt-in.
The tabs
Every event, newest first. Where you land when something just broke.
Errors grouped into problems, with triage, comments, and suspect commits.
Follow one request across services and see where the time went.
Latency percentiles per endpoint, so a slow tail is visible.
Health per deploy, and what likely caused a regression.
Scheduled checks that call your endpoints and tell you they're down.
Fire on a burn rate or a saved search, not on every error.
The query bar and filter builder every tab shares.
Getting started
- Enable it
Enable monitoring on project. See Setup.
- Rebuild your SDKs
Reporting connection is compiled in at build time. Already-published versions report nothing. Rebuild and publish SDKs.
- Enable reporting in application
SDK user sets
logging.enabledtotrue. It defaults tofalse, even after project toggle and rebuild. - Upload symbols
Otherwise production stack traces are unreadable. See Readable stack traces.
Live by default
Events stream to the dashboard as they arrive, so an incident updates in front of you without a refresh.
Credentials are scrubbed on the way out
Every runtime redacts credential-shaped keys and sweeps free text for tokens, JWTs, card numbers and email addresses before an event is sent. It's on by default. See Redaction.
What's kept
Raw events are kept 7 days on Free, 30 on Starter, 90 on Growth, 180 on Business and 365 on Enterprise by default (or Enterprise order-form window). Charts survive past raw-event expiry on hourly rollups.
Your plan includes a monitoring storage allowance; usage against it is shown in the dashboard.
Further reading
Background rather than instructions, on the blog.