Live tail
Watch a project's logs as they arrive, redacted and without storing them.
This page shows you how to watch a project's logs live, to check that an integration works or to follow a service while you reproduce a problem.
What it shows
Open a project and choose Live. Every log line the project receives after the page opens appears within about two seconds, at every level, trace and debug included, with the same redaction as the rest of dlogify: an email address shows as <email>. Each line shows its local time, level, service/environment and message; long messages are cut at 2 KiB.
Nothing is stored. Lines sent before you opened the page are not shown, and closing the page discards them. Every role can use live tail.
If no line arrives in the first 10 seconds, the page says it is waiting and links to the project's API keys, where the setup snippet is.
Filters
| Filter | Shows |
|---|---|
| Service | Only this service (exact match) |
| Environment | Only this environment (exact match) |
| Minimum level | This level and above: trace, debug, info (default), warn, error |
| Message contains | Messages that contain this text, ignoring case; it is plain text, not a pattern |
Filters are kept in the address, so you can share a filtered view. Changing a filter restarts the stream.
Pause, resume and clear
- Pause stops the list from moving; new lines keep arriving and a counter shows how many. Resume shows them.
- Clear empties the list.
- The page keeps the newest 1,000 lines and discards older ones.
- The list follows the newest line until you scroll up; Newest returns to the bottom.
Limits
| Free | Pro | Team | |
|---|---|---|---|
| Live tail sessions at once (per organization) | 1 | 5 | 20 |
| Lines per second (per session) | 50 | 200 | 500 |
| Session length | 15 minutes | 60 minutes | 60 minutes |
Each open Live page or API stream is one session. Opening one more than the plan allows returns plan-limit-reached with limit: "tail_sessions"; close a session in another tab and try again.
When lines arrive faster than the plan's lines per second, or faster than your browser reads them, the extra lines are skipped and the page says how many. Narrow the filters to see fewer lines.
Gaps and repeats
Live tail is best effort. A line can occasionally be missing, for example during a restart, and a line can occasionally appear twice when a batch of logs is processed again. Tickets, error groups and summaries are not affected.
When a session ends
A session ends when it reaches the plan's session length, when you lose access to the project or the project is deleted, and when the service restarts. After a network error or a restart the page reconnects on its own, up to three times; otherwise choose Reconnect.
From a script
The page reads GET /v1/projects/{project_id}/tail, a Server-Sent Events stream, with your session. The same filters are query parameters:
curl -N -H "authorization: Bearer <session token>" "https://api.dlogify.com/v1/projects/prj_01j…/tail?level=debug"The stream sends lines events with an array of lines, dropped events with the number of skipped lines and why, and an end event with the reason just before it closes. API keys cannot open a live tail.