Skip to content

Vulnerability Processing Taking Longer than expected #16858

@mostlikelee

Description

@mostlikelee

Fleet version: 4.44.0

Web browser and operating system: NA


💥  Actual behavior

Vulnerability processing was observed taking 2x longer after upgrade to v4.44.0 in some Fleet Cloud instances.

🧑‍💻  Steps to reproduce

Slack thread reference: https://fleetdm.slack.com/archives/C019WG4GH0A/p1707682626450799

This was observed with CPU utilization and spotchecked observing created_at and updated_at timestamps for vulnerability cron jobs in the database.
image

🕯️ More info (optional)

An increase in scan time is expected when upgrading to 4.44.0 due to the addition of OS vulnerability scans, but 2x seems excessive. As observed in one cloud hosted environment, the total OS count was ~40, and primarily macOS devices.

QA Testplan

  1. Run vuln processing before this change and note the vulns identified.
  2. Run vuln processing after this change and compare to the above.

Metadata

Metadata

Assignees

Labels

#g-endpoint-opsEndpoint ops product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedcustomer-pingali~released bugThis bug was found in a stable release.~vulnerability-management

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions