mudler / yip

:pushpin: Yaml Instructions Processor - Simply applies a cloud-init style yaml file to the system

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Add an id to the logging output

Itxaka opened this issue · comments

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

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