Logs
Logs is every event your SDKs reported, 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 | Stored event after client and ingest redaction |
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.
Quick filters
Above the list, Errors, 5xx, 4xx and Slow (>1s) narrow the stream in one click.
Live updates
Turn on Stream new events as they arrive to watch events come in, without refreshing. From the CLI, use octri monitoring logs.
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 the window in your Enterprise order form). Charts over longer ranges use hourly rollups; individual events expire at your plan's raw window.
Sensitive data
Common sensitive keys (passwords, tokens, secrets) are stripped from events automatically before they're stored.
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.