Daniel Basner
05/10/2023, 9:49 PMRunRecord
s using context.instance.get_run_records
however that just gets me the status of the run for an entire job, not the individually failing/succeeding operations inside that job.
Separately, I know that I could query dagster's postgres instance, such as the runs
table, but this too does not contain individual operation results. I know that this information must exist somewhere in there since we can see the state of individual operations in runs in dagit.
Also, is there a way to force local runs to use our production PostgresEventLogStorage
instead of SqlEventLogStorage
? We use postgres in our production environment, and I'd love to be able to query that data from my local machine to try out queries.