You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JSON logging format is outputting wrongly JSON formatted data for the key run_result inside the logs/dbt.log file. It might be that everything inside that key is being escaped as a string
Expected Behavior
I'm expecting to be able to extract data from data.run_result after running a dbt model. It seems like the data in run_result ends up being shown at the end of the run in the run results.json file, but we could use it without waiting to the end of the run for when we have long daily runs and we want to monitor the status of the load
Steps To Reproduce
Run the following from the command line (changing to what model you want to test). Then try to load the result
dbt --log-format json run --target uat --model any_model
cat logs/dbt.log | grep run_result | jq -r .data.run_result # this works
cat logs/dbt.log | grep run_result | jq -r .data.run_result | jq .status # this errors out not being able to load the previous log info
github-actionsbot
changed the title
[Bug] JSON logging format outputs incorrect JSON for run_result
[CT-623] [Bug] JSON logging format outputs incorrect JSON for run_result
May 10, 2022
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.
Is there an existing issue for this?
Current Behavior
The JSON logging format is outputting wrongly JSON formatted data for the key run_result inside the
logs/dbt.log
file. It might be that everything inside that key is being escaped as a stringExpected Behavior
I'm expecting to be able to extract data from
data.run_result
after running a dbt model. It seems like the data inrun_result
ends up being shown at the end of the run in the runresults.json
file, but we could use it without waiting to the end of the run for when we have long daily runs and we want to monitor the status of the loadSteps To Reproduce
Run the following from the command line (changing to what model you want to test). Then try to load the result
Relevant log output
Environment
What database are you using dbt with?
bigquery
Additional Context
I'm trying to upload these logs to ElasticSearch but having issues processing it
The text was updated successfully, but these errors were encountered: