Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an id to the logging output #117

Open
Itxaka opened this issue Oct 17, 2023 · 1 comment
Open

Add an id to the logging output #117

Itxaka opened this issue Oct 17, 2023 · 1 comment

Comments

@Itxaka
Copy link
Collaborator

Itxaka commented Oct 17, 2023

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

@mudler
Copy link
Owner

mudler commented Oct 17, 2023

it should be already there (printed with debug mode)

opName := fmt.Sprintf("%s.%s", rootname, name)
however that name is for the whole "stage" in a file, not for the single step

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants