-
Notifications
You must be signed in to change notification settings - Fork 870
Vulnerability Processing Taking Longer than expected #16858
Copy link
Copy link
Closed
Labels
#g-endpoint-opsEndpoint ops product groupEndpoint ops product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedSomething isn't working as documentedcustomer-pingali~released bugThis bug was found in a stable release.This bug was found in a stable release.~vulnerability-management
Milestone
Metadata
Metadata
Assignees
Labels
#g-endpoint-opsEndpoint ops product groupEndpoint ops product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedSomething isn't working as documentedcustomer-pingali~released bugThis bug was found in a stable release.This bug was found in a stable release.~vulnerability-management
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_atandupdated_attimestamps for vulnerability cron jobs in the database.🕯️ 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