Logs
Logs shows events reported after project monitoring and SDK-user reporting are enabled, newest first. It's the raw material behind every other tab, and where you land when something just broke.
Narrowing it down
The unfiltered stream is noise. Use the filter builder or type a query:
level = 'error' AND statusCode >= 500 ORDER BY timestamp DESCSee Search and filters for the fields and operators.
Reading an event
Opening an event shows what the SDK captured:
| Level | debug, info, warning, error, fatal |
| Status | The HTTP status returned |
| Latency | How long the call took |
| Operation | Which endpoint, by its method name |
| Environment | Which project the event belongs to |
| Fingerprint | What groups this event into an issue |
| Stack trace | Where it failed, resolved to your source if symbols are uploaded |
| Context | Structured data attached by the SDK |
| Raw event | Event as stored after client and ingest redaction; sensitive fields are not recoverable |
Two events with the same fingerprint are the same problem. When a log line looks familiar, its fingerprint tells you whether it really is the issue you already triaged.
Live updates
New events stream in as they arrive. During an incident you can watch it happen rather than refreshing.
Logs, or Issues?
Both show errors, and reaching for the wrong one wastes time.
| Use | When |
|---|---|
| Logs | You want individual events. "What exactly did that request do?" |
| Issues | You want problems. "What's broken, and for how many people?" |
Ten thousand log lines are one issue. Start at Issues to know what's wrong, come to Logs to see a real example of it.
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 over longer ranges read hourly rollups; individual events expire with plan's raw-event window.
Sensitive data
Client and ingest redaction strip common sensitive keys, including passwords, tokens, secrets and user.email, before storage. filterPii defaults on in SDK reporting configuration.
The automatic list knows password and token. It cannot know context.customerReference holds something sensitive, and an error message that interpolates a key is just a string to it.
Don't send what shouldn't be stored. Redaction is the safety net, not the plan.