livepeer / livepeer/go-livepeer
Add support for some type of error log filtering to make it easier to just sift through errors
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
On one hand enabling more verbose logging helps with understanding what is happening on the node, on the other hand it makes it really difficult to sift through actual error logs.
What is a good way to make it easy to *just* access error logs? Maybe have an option to pipe error logs specifically to a file?
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
No files, tests, or entry points are identified in the issue. First clarify the desired filtering or separate-file behavior and review the node's existing logging configuration; done means an agreed, usable way to access only error logs without losing verbose logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100