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

Ensure that all dbt invocations have an invocation_id #4337

Closed
gshank opened this issue Nov 24, 2021 · 0 comments · Fixed by #4340, #4351 or #4359
Closed

Ensure that all dbt invocations have an invocation_id #4337

gshank opened this issue Nov 24, 2021 · 0 comments · Fixed by #4340, #4351 or #4359
Assignees

Comments

@gshank
Copy link
Contributor

gshank commented Nov 24, 2021

This is a sub-issue of #4260.

In order to make sure we can distinguish logs from different runs we should always have an invocation_id. If tracking is off, it isn't created today so we would need to create it. (to add it to logging, add it as a class property on the superclass) (previously considered: preserve process id like it is today, global run_id reported at start, or allow some sort of user markers).

@gshank gshank self-assigned this Nov 24, 2021
iknox-fa pushed a commit that referenced this issue Feb 8, 2022
iknox-fa pushed a commit that referenced this issue Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment