CarlosJuncher03 opened a new issue, #6245: URL: https://github.com/apache/hop/issues/6245
### What would you like to happen? Hello Apache Hop maintainers, I’d like to request a small but very impactful UI improvement in Hop GUI: add visual highlighting for log lines by severity in the “Logging” panel (e.g., render ERROR lines in red, WARN in orange/yellow, INFO in default color). Current behavior In the Hop GUI “Logging” tab, log entries are shown as plain text. Even when errors occur (e.g., stack traces), the user must manually scan the text to spot the first ERROR line or the root cause. Filters help, but they don’t make mixed logs visually “parseable” at a glance. <img width="2774" height="1256" alt="Image" src="https://github.com/user-attachments/assets/cee17b14-8c4f-41a8-aa2f-624649259787"; /> Proposed improvement Add severity-based styling in the Logging view: ERROR (and FATAL) → red WARN → orange/yellow INFO → default DEBUG/TRACE → gray (optional) Optionally: a toggle in Preferences (“Enable log highlighting”) and/or a context menu option in the Logging panel. Why this matters Faster troubleshooting: In real pipelines, a single run can produce thousands of INFO lines. Highlighting errors makes the root cause visible immediately. Reduces operational mistakes: When monitoring runs, operators can miss critical ERROR lines hidden inside verbose logs. Improves usability for new users: Beginners often don’t know where to look first; visual cues guide them. Better accessibility: Color + optional icon/bold/underline improves recognition (and can be paired with non-color cues for color-blind users). Example scenario When a transform fails to initialize and prints a stack trace, the ERROR lines are present but not visually distinct. Highlighting would make the failure point obvious without searching the text. If you agree with the direction, I can provide screenshots and additional details about the use case. Thank you. ### Issue Priority Priority: 3 ### Issue Component Component: Hop Gui -- 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]
