Previously, the schedule log command only showed the top level log file, which captured errors at the cron and bash script level. This diff updates the schedule log command to also link to the individual execution logs, which are needed to debug user-code error issues.
Details
Details
- Reviewers
dgibson - Commits
- R1:d777cb267fac: Add more detail to schedule logs command
Run dagster schedule logs in the toys directory for (1) a schedule with result logs and (2) a schedule without result logs
Diff Detail
Diff Detail
- Repository
- R1 dagster
- Branch
- fix-logs
- Lint
Lint Passed - Unit
No Test Coverage
Event Timeline
| python_modules/dagster/dagster/cli/schedule.py | ||
|---|---|---|
| 373 | not really related to this diff but should we also gate this function on specific schedulers? It doesn't work with the daemon scheduler for example - does it work with the k8s scheduler? | |
| python_modules/dagster/dagster/cli/schedule.py | ||
|---|---|---|
| 373 | yes we should, how do the logs for the daemon scheduler work? | |