When developing, It can be quite useful to know what exactly was sent to the database or, in the case of Hibernate Search, to Elasticsearch.
Currently, the only options to do so are through logs.
I think a dedicated Dev UI interface could increase developer joy significantly, especially if we introduce additional features. A few that come to mind (though we may not end up implementing all of them):
More user-friendly display: e.g. show SQL and bind parameter values next to each other, instead of in separate log lines
Easy export: "copy" buttons, e.g. for Elasticsearch in a format suitable for pasting into Kibana (see also #39582)
Replay: re-run SQL or Elasticsearch requests, possibly after a manual edit, and display results
Context: show the stack trace that led to a particular statement/request. Or maybe just rely on some OpenTelemetry tracing integration?
Timing: how long did a given request take?
Search: filter by endpoint, sort by query time, ... Though that could require rather heavy infrastructure.
Description
When developing, It can be quite useful to know what exactly was sent to the database or, in the case of Hibernate Search, to Elasticsearch.
Currently, the only options to do so are through logs.
I think a dedicated Dev UI interface could increase developer joy significantly, especially if we introduce additional features. A few that come to mind (though we may not end up implementing all of them):
Implementation ideas
No response