Add an id to the logging output
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 34
- Avg merge
- 14h 10m
- Merged PRs (30d)
- 5
Description
Currently with the ned DAG and all, there is a lot of logging and sometimes it makes it difficult to know what is from where, especially if debug is enabled.
I propose some kind of ID logged along the lines, that refers to that step only so it can easily be tracked at a glance and even grepped easily to only get the logs for that ID. Kind of what its done on threaded apps where you want to track just one query along the system.
Not sure if the DAG already sets a unique identifier per task that could be used? @mudler
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.
Research direction
Start by locating the DAG task execution and logging entry points, then check whether each task already has a unique identifier. Define how the identifier should be assigned and formatted; done means logs for a task consistently include an identifier that can be grepped independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100