Question: does parsing status logs still requires this "hack"
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 433
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
I am wondering whether this piece of code is still needed?
https://github.com/osquery/osquery-go/blob/629f995b6947feead99bd17af26c45c269f3bbbd/plugin/logger/logger.go#L73-L76
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 reading the referenced section of plugin/logger/logger.go at lines 73-76 and trace how status logs reach it. Check the surrounding logger flow and project history to determine whether the hack is still required. Done means reaching a clear decision and documenting or implementing the resulting cleanup with appropriate validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100