Logs
Logs overview
What is stored, where, and how it stays yours.
Status: preview
For a live application, DevSewa ships events to the fleet log manager under the canonical tenant and reads them back for you. A test application stores simulated events only in DevSewa’s application-scoped sandbox; it creates no Log Manager store. The application is resolved from the client secret, so no request parameter can name another tenant.
What an event looks like
A JSON object with a
message and optional severity (debug, info, notice, warning, error, critical), source_type, source_id, server_id, request_id, trace_id, labels and fields. Timestamps default to arrival time; send timestamp_ms to keep your own.Retention and search
- Events are kept for the store’s retention window (30 days during preview) and deleted by a scheduled cleanup you can see in stats.
- Full-text search matches the message as one phrase; filters narrow by severity, source, server and time.
- Pagination is a cursor over
(timestamp, event id): stable under new arrivals.