Currently dagu limits history for dag run by number of days by defining configuration at global level via base.yaml or individual dag levels. This feature is very useful for cron jobs. For non cron jobs, it may never get used. For non cron jobs, the history of dag runs should be limited by the number of runs rather than number of days.
As suggested by @yottahmd, we can add something like this:
historyRetention:
runs: 3 # Limit by runs
days: 5 # Limit by days
Currently dagu limits history for dag run by number of days by defining configuration at global level via base.yaml or individual dag levels. This feature is very useful for cron jobs. For non cron jobs, it may never get used. For non cron jobs, the history of dag runs should be limited by the number of runs rather than number of days.
As suggested by @yottahmd, we can add something like this: