great talk at coalesce this morning @Emily!

Link to video?

Found it, thanks.

thank you so much!! glad you could attend 🙂

We've been considering switching over to using the

run_results.json

for our monitoring as well. Do you know if the

run_results.json

contains the dbt invocation id? Being able to link groups of nodes together within an invocation is important for our existing monitoring setup

hmm ill look into that

how do y'all currently group nodes together within an invocation? Im assuming that you do considering that IIRC there was a number on your looker dashboard showing you the avg total runtime (or something like that)

ah yeah so we just have one big dbt run each morning, so its just grouped based on the timestamp/date of the overall run

ah! okay that makes sense. thanks @Emily

no problem! i checked run_results and i dont see any sort of ID for the run, but i could pass along that feedback to the fishtown team

@Emily I think there are probably enough ways around it. Even just prefixing the

run_results.json

in s3 with a UUID should be enough since I think a single

run_results.json

is 1:1 with an invocation anyway. Is that your understanding as well?

yes im pretty sure thats the case