dbt run results visualizer
See where a dbt run actually spent its time
Every dbt invocation writes a full account of itself to target/run_results.json: what ran, on which thread, for how long, and how it ended. This reads that file and draws it. The file never leaves your browser, so you can use it on a work artifact without asking anyone.
Drop run_results.json here
Parsed in the page with JavaScript. There is no upload, no server, and no analytics event carrying anything from your file.
Where the file is
- dbt Core writes it to target/run_results.json in your project after every run, build, test or seed.
- dbt Cloud has it under the Artifacts tab of any run, next to manifest.json.
- In CI, it is whatever your job archived from the target directory.
The sample loads on arrival so there is something to read before you go and find your own file. Real node names from the lab repo, invented timings, generated by scripts/make-sample-run.mjs.