Richard Fisher
12/14/2020, 8:07 AM$DAGSTER_HOME/schedules/logs/<schedule_id>/
I was hoping to be able to do something like this in the dagster.yaml file:
scheduler:
module: dagster_cron.cron_scheduler
class: SystemCronScheduler
config:
base_dir: /var/lib/persistent_storage
I’ve set up the event_log_storage, which contains most of the same info, but it would be good to have the schedule logs as well.Istvan Darvas
12/14/2020, 12:58 PMevent_log_storage in dagster yaml
Richard Fisher
12/14/2020, 1:13 PM$DAGSTER_HOME/schedules/logs/<schedule_id>/
to schedule.log (with some other info in <timestamp>_<schedule_id>.result
. I was hoping that there was additional info logged there, specifically about how the cron schedule is behaving, rather than just the output logged from events. But, it seems that everything in $DAGSTER_HOME/schedules/logs/
is just used for Inter Process Communication, but it would be good to have someone from the Dagster team confirm this.alex
12/14/2020, 3:53 PMschedule_storage
section of config. That DB holds our “tick” structure which is what we use to track when cron has fired and capture any errors related to kicking off the scheduled run.0.10.0
release with our new scheduler which @daniel can answer any questions aboutdaniel
12/14/2020, 4:04 PMRichard Fisher
12/15/2020, 6:10 AM0.10.0
until trying to incorporate this.