Details
-
New Feature
-
Status: To Do
-
L3
-
Resolution: Unresolved
-
None
-
None
-
None
-
SR4J Sprint 127 (6.56), SR4J Sprint 128 (6.57), SR4J Sprint 129 (6.58)
-
70.8
Description
Currently the execution history shown for each configuration will only contain executions for the current node handling the HTTP request.
The above means it is not possible to see executions that happened on other nodes in the cluster, or their logs.
For the Performance charts, we give the option to filter by specific node, perhaps we should have something like that here, and merge the results by default.