Improve error handling in the Fleet UI when /status/live_query endpoint returns an error.

[randalmichael]

Fleet version (Head to the "My account" page in the Fleet UI or run fleetctl version): 3.10.1
Operating system (e.g. macOS 11.2.3): Linux 7.5
Web browser (e.g. Chrome 88.0.4324): Chrome

---

🧑‍💻  Expected behavior

When I select the Queries tab, then click on Add new query I get an error message saying Live queries disabled due to error.

💥  Actual behavior

This is the screen I get:

More info

Here are the errors in the browser:

[noahtalerman]

@randalmichael thank you for including the screenshots of your "Console" table.

I see the "Websocket is closed before the connection is established" warning. The Fleet UI uses websockets to relay live query results. It looks like the requests to the /websocket endpoints are failing for your Fleet instance.

Do you mind pasting a screenshot of your browser's "Network" tab?

[randalmichael]

I only get this error on my DEV system. PROD system has no error.

How do I get to the Network Tab of the browser?

[randalmichael]

Here it is:

[noahtalerman]

Ah, you'll first have to open the "Network" tab and then refresh the page. This way we'll be able to see the status of each request made by the Fleet UI.

Are both your DEV and PROD instances running Fleet version 3.10.1?

[randalmichael]

[randalmichael]

Now it does not have an error.

[noahtalerman]

Now it does not have an error.

Ok, so it looks like you had to click through the "Your connection is not private" on your dev instance to dismiss the live query error. Is this correct?

[randalmichael]

Correct

[noahtalerman]

@randalmichael I've altered this issue to reflect improvements that can be made to Fleet based on your experience.

Goal

As a Fleet user, I want to know why live querying is disabled so that I can attempt to resolve the issue or provide better context when filing an issue.

Solution

Improve error handling when the api/v1/fleet/status/live_query returns an error.

[noahtalerman]

Closing because the issue was resolved.

The above improvements will be reconsidered if the frequency with which users experience the error increases.