-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
Context:
When the status websocket cannot be created successfully we currently see a missing engine-status in the Page Footer but a green elasticsearch status, see the attached screenshot.
Possible causes of a broken websocket might be misconfigured proxies so it would be useful to make this issue more transparent to the user.
Given:
I open Optimize in the browser
When:
The status Websocket connection cannot be established
Then:
I see no engine status in the footer but a green elasticsearch status (which might be wrong)
Expected:
I either see an error indicating that the status cannot be retrieved due to the websocket issue or I see the current status at the time of page reload retrievable from the HTTP /api/status endpoint + a hint that updates cannot be performed due to websocket connection issues
