Dashboard page only shows 100 DAGs

[jonathonc]

The dashboard page only shows 100 DAGs, even if there are more than 100 DAGs in the system

It looks like there is a default limit of 100 here (which is reasonable)

dagu/internal/client/client.go

Line 311 in 678dd21

limit := 100

I can see the API has support for increasing the limit api/v1/dags?limit=xxxx

Thoughts on this? I appreciate we may not want to get all the DAGs in case there are a lot in the system.

What is restricted it to only DAGs executed within the day? Or maybe this time period can be controlled?

Happy to help with a PR, but keen to see how you might want to approach a possible solution.

[yottahmd]

Thank you very much for submitting the issue and showing interest in contributing a PR! Your input is really helpful.

Currently, when a large number of DAG files are created, performance issues arise due to the need to load a significant amount of data. To address this, I plan to change the storage structure. With the upcoming release of the v2.0 alpha version, I would like to ensure that all DAG execution data for the current day is reflected on the dashboard.

As a temporary workaround, I think that allowing configuration for the page limit might be an idea. If you're interested in contributing a PR, it would be very welcome.

To add config key in the configuration, the following files would need to be modified:

• Add a perPage key and DAGU_PER_PAGE environment variable to the config (to change the default upper limit):
  

  dagu/internal/config/config.go

  Lines 34 to 62 in 10b0c69

  	type Config struct {
  	Host string // Server host
  	Port int // Server port
  	DAGs string // Location of DAG files
  	Executable string // Executable path
  	WorkDir string // Default working directory
  	IsBasicAuth bool // Enable basic auth
  	BasicAuthUsername string // Basic auth username
  	BasicAuthPassword string // Basic auth password
  	LogEncodingCharset string // Log encoding charset
  	LogDir string // Log directory
  	DataDir string // Data directory
  	SuspendFlagsDir string // Suspend flags directory
  	AdminLogsDir string // Directory for admin logs
  	BaseConfig string // Common config file for all DAGs.
  	NavbarColor string // Navbar color for the web UI
  	NavbarTitle string // Navbar title for the web UI
  	Env sync.Map // Store environment variables
  	TLS *TLS // TLS configuration
  	IsAuthToken bool // Enable auth token for API
  	AuthToken string // Auth token for API
  	LatestStatusToday bool // Show latest status today or the latest status
  	BasePath string // Base path for the server
  	APIBaseURL string // Base URL for API
  	Debug bool // Enable debug mode (verbose logging)
  	LogFormat string // Log format
  	TZ string // The server time zone
  	Location *time.Location // The server location
  	}

• Add configuration items to the frontend:
  

  dagu/internal/frontend/server/templates.go

  Lines 65 to 93 in 10b0c69

  	func defaultFunctions(cfg funcsConfig) template.FuncMap {
  	return template.FuncMap{
  	"defTitle": func(ip any) string {
  	v, ok := ip.(string)
  	if !ok || (ok && v == "") {
  	return ""
  	}
  	return v
  	},
  	"version": func() string {
  	return constants.Version
  	},
  	"navbarColor": func() string {
  	return cfg.NavbarColor
  	},
  	"navbarTitle": func() string {
  	return cfg.NavbarTitle
  	},
  	"basePath": func() string {
  	return cfg.BasePath
  	},
  	"apiURL": func() string {
  	return path.Join(cfg.BasePath, cfg.APIBaseURL)
  	},
  	"tz": func() string {
  	return cfg.TZ
  	},
  	}
  	}

• Modify base HTML template
  

  dagu/internal/frontend/templates/base.gohtml

  Lines 10 to 19 in 10b0c69

  	function getConfig() {
  	return {
  	apiURL: "{{ apiURL }}",
  	basePath: "{{ basePath }}",
  	title: "{{ navbarTitle }}",
  	navbarColor: "{{ navbarColor }}",
  	version: "{{ version }}",
  	tz: "{{ tz }}",
  	};
  	}

• Related frontend files

I also welcome any alternative ideas for the workaround. :)

[yottahmd]

Thank you for the contribution. Closing as it's completed.