PreviewYour backend’s logs, searchable, isolated per application.
Send log events from your backend with the application’s client secret and read them back from the console or the API: filter by severity, source and time, full-text search, retention you can see. Test and live environments never share a store, and no other customer’s logs are ever in the same file.
ship an event · your backend
curl https://logs.api.devsewa.com/v1/logs/ingest \
-H "Authorization: Bearer $DEVSEWA_CLIENT_SECRET" \
-H "content-type: application/json" \
-d '{"severity":"error","source_id":"api","message":"payment webhook failed","request_id":"req_8f1c"}'
→ { "status": "ok", "inserted": 1, "duplicate": 0 }
GET https://logs.api.devsewa.com/v1/logs?severity=error&text=webhook
→ { "events": [ … ], "next_cursor": "" }What you get · preview
Logs, without running it.
Served from logs.api.devsewa.com and managed from the console. Backed by LOG_MANAGER_APP, mediated by the DevSewa control plane. In preview: it opens for early-access customers as the fleet pairing for their account completes.
- One call to ship an event or a batch of up to 500
- Severity, source, server and time filters; full-text search
- Cursor pagination that never skips or repeats
- Per-application stats: totals, by severity, top sources
- Test and live environments stored separately
- Retention per store; nothing is deleted early
Isolation
How it stays yours.
- Store
- One database per application environment on the fleet log manager
- Tenant
- Set by DevSewa from your application; a request can never name another
- Credential
- DevSewa’s own trusted-app token; your client secret never leaves DevSewa
Still to come
- Alert rules that mail or SMS you
- Log shipping from DevSewa-hosted servers automatically
Add Logs to your application.
Create an account, register a test application and exchange your first ticket in under ten minutes.