design affordances for logs from multiple sources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
From a user:
"Sometimes you have a log that shows A B A B A B A B A B. For me, I’d prefer A: <5 lines>, B: <5 lines>. Maybe with a + in the log to expand."
I've personally noticed that logs can be very hard to understand when they're interspersed a lot, e.g.,
- logs from different builds
- logs from multiple containers in the same pod
We should do something better to make logs "stick" together a bit better, or offer some UI buttons to make it easier to group them in-place
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
The issue names no files, tests, or entry points. Start by locating the log display and reviewing how logs from builds or multiple containers are interleaved; define the proposed grouping and expansion behavior and its acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- frontend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100