initial web load should stream logs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Currently, when you visit http://localhost:10350/, the webview's initial pageload contains all the logs we've seen so far (up to a maximum payload).
But it would be too slow to display those logs all at once, so it:
- Only renders a window of the logs
- Incrementally streams new logs as they come in
The problem with this approach is that the initial web load takes much longer than it should.
We currently work-around this issue by capping the max logs in the logstore. But a better approach would be to only load the first "window" of logs in the initial payload, and backfill the historic logs as we need them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the webview's initial page-load payload and the logstore's existing log-window and incremental-streaming paths. Determine where historic logs can be requested or backfilled, then verify that the initial load contains only the first window while older logs appear as needed without breaking new-log streaming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100