fleet
fleet copied to clipboard
Improve database performance of vulnerability processing job
Logic used for ingesting software is not handling duplicated software on host
This usually happens when ingesting Python/Ruby/etc packages. If we have the same package installed more than once on different envs - for example the six 1.15.0 - we only store a single row in the software table for that package, because of this, every time we are ingesting software, the ingestion logic will incorrectly determine that there are new software on the host, thus triggering a DB sync - which is not ideal from a performance point of view.
@zayhanlon This bug has aged out and is moving back to product drafting.
@zhumo Reminder that when moving an item out of product drafting, remember to remove the :product label so it is removed from the product board.
@lukeheath That's for bugs only, right? All bugs should go through the bug board instead of the drafting board, except when it is in drafting by product?
@zhumo Yes, this only applies to bugs that return to product drafting, and then come back to engineering.
This bug has aged out. Moving back to drafting.
Bug has aged out. Moved back to drafting
Bug has aged out. Moved back to drafting
Bug has aged out. Moving back to product drafting.
Hey @ksatter, I pulled this engineering initiated story off the feature fest board.
Eng initiated stories don't need to go through feature fest. Check out the process here.
FYI @lukeheath
@sharon-fdm I'm removing the bug label. We decided this is not a bug back in 2023, so it's been sitting and not been triaged as a bug. This was triaged, instead, as an engineering-initiated story. I'm removing the bug label because it's a very old story (which is okay) but not a very old bug (which is not okay).
Hey @zayhanlon, this customer request has shipped.
Ingestion logic tweaked, Swift as a cloud city's breeze. No more dupes, more peace.