Cached query results on Host details page are missing

[noahtalerman]

Fleet version: Fleet 4.48

---

💥  Actual behavior

Cached query results show val as the result for all columns:

🧑‍💻  Steps to reproduce

Not sure.

🕯️ More info (optional)

Looks like it's a frontend bug. The GET /hosts/:host_id/queries/:query_id is returned results:

[lukeheath]

@noahtalerman @sharon-fdm Reminder that per our high-priority stories and bugs documentation, all P-rated tickets should be assigned to the release ritual DRI (me) first, before being actioned. I then validate they meet the criteria before assigning them to the EM for action. If it's a P0 or P1, DM me on Slack or text me via phone so I can review it immediately.

[fleet-release]

Missing query cache,
Fixed, clarity in data,
Truth within reach now.

[noahtalerman]

Sharon: Following this bug, we found out that no customer is using it. Maybe there is something we could iterate on it to make it more attractive?

Noah: Is that true? I think we don’t know who is using it. We only know that Uber and Fastly aren’t using it (yet). Uber hasn’t upgraded and Fastly was concerned about DB load.

Discoverability problem: Rachael: Maybe we can light up hostnames on the query report page so folks know that you can see reports at the host level.

Demo problem: Help folks know this exists

• Dave: For IT, it would be exciting to show the most intensive processes (CPU and memory).

FYI @sharon-fdm here's what we discussed during product office hours on 2024-05-06

[sharon-fdm]

@noahtalerman After doing the postmortem on this, we found that it was a specific page showing the results per host. So perhaps this specific page was not used, or maybe it was used and was not important for the customer to report since the functionality as a whole was working 🤷 ...?

[noahtalerman]

@sharon-fdm I ran into the bug before any users reported it.

We don't know if a customer/user ran into the bug. It's possible they did.