Feature Request: Built-in Dashboard for Spring Batch

Expected Behavior

Spring Batch should provide a built-in, lightweight web dashboard (similar to JobRunr's dashboard), enabled with a single property:

spring.batch.dashboard.enabled=true

Key capabilities:

1. Job Overview — All jobs with latest status, execution counts, and average duration.
2. Execution Details — Drill-down into JobExecution with step-level read/write/skip counts and exception stack traces.
3. Real-time Monitoring — Live progress for running jobs (items processed, throughput, ETA).
4. History & Search — Filterable JobInstance/JobExecution history (by name, status, date range, parameters).
5. Manual Operations — Restart, stop, and abandon executions directly from the UI.
6. Partitioned Step Visibility — Partition-level progress to identify stragglers.

Built on existing JobRepository/JobExplorer APIs, zero additional infrastructure, shipped as an optional spring-boot-starter-batch-dashboard.

JobRunr's dashboard:

Current Behavior

Spring Batch has no built-in UI. Current workarounds are all unsatisfactory:

• Direct SQL against BATCH_JOB_EXECUTION tables — cumbersome and not operator-friendly.
• Spring Cloud Data Flow — heavyweight platform, overkill for embedded batch monitoring.
• Custom REST + UI on JobExplorer/JobOperator — duplicated effort across the community.
• Spring Batch Admin — deprecated since 2017, no replacement.
• Actuator/Micrometer — aggregated counters only, no execution-level detail or operational actions.

The JobRepository already persists all data needed for a dashboard, but there is no standard way to visualize it.

Context

Every Spring Batch team in production needs operational visibility into job status. Without a built-in dashboard, teams are forced to either build custom UIs, adopt the heavyweight SCDF, or query metadata tables via SQL. This is duplicated effort across the entire community.

JobRunr proves this is achievable — frontend bundled in JAR, enabled with one property (jobrunr.dashboard.enabled=true). Spring Batch could adopt the same approach with an optional starter module.

Start by reviewing the existing JobRepository and JobExplorer APIs and the proposed spring-boot-starter-batch-dashboard boundary. Define the dashboard scope, UI and operational integration points, then establish how all six requested capabilities would be validated before implementation begins.