-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Comments
gshank
added a commit
that referenced
this issue
Nov 24, 2021
gshank
added a commit
that referenced
this issue
Nov 24, 2021
4 tasks
gshank
added a commit
that referenced
this issue
Nov 24, 2021
gshank
added a commit
that referenced
this issue
Nov 24, 2021
gshank
added a commit
that referenced
this issue
Nov 24, 2021
4 tasks
4 tasks
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
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).
The text was updated successfully, but these errors were encountered: