Skip to content

List script timeout on specific hosts due to large number of script results #32295

Description

@mason-buettner

Fleet version: 4.72

Web browser and operating system: Chrome 139 on Windows 11 Pro 24H2


💥  Actual behavior

customer-ampella reports that hosts with a high number of host_script_results records fail to return the list of available scripts to run. When they attempt to navigate to the run script action (https://dogfood.fleetdm.com/hosts/HOST/details > Actions > Run script), the dialogue hangs and then displays an error as shown below:

Image

When attempting to list scripts for one of the problematic hosts, the request hangs and times out.

🛠️ To fix

TBD

Product designer: _________________________

🧑‍💻  Steps to reproduce

  1. Identify a host with a high number of records in the host_script_results table.
  2. Attempt to list the scripts available to run on the system either via the UI or the API.
  3. Observe timeout.

🕯️ More info (optional)

The hosts customer-ampella sees this behavior on have over 40,000 records in the host_script_results table. The query and redacted results used to identify affected hosts:

SELECT host_id, COUNT(*) as Totals FROM host_script_results group by host_id ORDER BY Totals ASC ;
|   [host_id_0] | 42526 |
|   [host_id_1] | 46263 |

I have been unable to personally reproduce due to a lack of access to an environment with an equivalent number of records in the specified table.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

#g-orchestrationOrchestration product groupP2Urgent: Supported workflow not functioning as intended, newly drafted feature with urgent Fleet needbugSomething isn't working as documentedcustomer-ampellacustomer-preston

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions