Adding logging to all the plugins.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- observability-sre
Research direction
Start by locating the plugin entry points and checking how plugins currently perform actions or emit output. Define the shared logging function's interface and the action events each plugin must report. Done means all plugins produce structured JSON action logs that can be consumed consistently.
Written by the indexing model from the issue text.
Description
Don't need easy to filter logs, just action logs, probably a simple function that is passed to all the plugins that can be called to log a json object.
- Dominant language
- Python
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from tinygrad/tinymod
-
Add Tags! Open
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Message Filtering OpenHigh Priority
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Raid behaviour Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in tinygrad/tinymod
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100