CarlosJuncher03 opened a new issue, #6904:
URL: https://github.com/apache/hop/issues/6904
### What would you like to happen?
Currently, Apache Hop provides real-time execution metrics through the
"Execution Information" tab. However, this data is volatile. Once the tab is
closed or the Hop GUI is restarted, the performance history of that specific
Pipeline or Workflow is lost unless an external monitoring stack is configured.
The Proposal (Phase 1):
Instead of a complex dashboard, I propose a simple Local Execution History
table integrated into the Pipeline/Workflow run configuration or a new
dedicated tab.
Key Requirements for this MVP:
Local Persistence: Hop should store the metadata (Status, Start/End
Time, Duration, Rows Read/Written) of the last 20–50 executions locally (e.g.,
in an internal H2 database or a simple JSON/LevelDB file).
History Table: A simple grid view where the user can see:
Execution Date/Time
Total Duration
Status (Success/Error)
Read/Write/Errors counts
Session Persistence: This history must persist even after restarting the
Hop GUI.
Why this is important (Arguments):
Performance Awareness: Developers need to know if a transformation is
getting slower over time without manually taking notes.
DataOps Foundation: Integrated observability is a core requirement for
modern ETL tools.
Debugging: Having a record of the last successful run vs. the current
failed run is essential for quick troubleshooting.
Future Scope (Phase 2):
Once this history is available in the GUI, we can later implement
side-by-side comparisons and trend charts.
### Issue Priority
Priority: 3
### Issue Component
Component: Transforms
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
