Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

Issue 2099 enable vulnerability processing new installs (#3104)

Browse Source 
* Enable vulnerability processing by default

* Add changes file

* Remove wrong env var

* Fix import

* Fix tests

* Update log line

* Remove unneeded import
This commit is contained in:
Tomas Touceda
2021-12-03 14:44:57 -03:00
committed by GitHub
parent 4c19c9c8b1
commit 142006cbdd
11 changed files with 22 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/01-Using-Fleet/13-Vulnerability-Processing.md
+2 -9
View File
@@ -28,8 +28,7 @@ The matching occurs server-side to make the processing as fast as possible, but
For example, when running a development instance of Fleet on an Apple Macbook Pro with 16 cores, matching 200k CPEs against the CVE database will take around 10 seconds and consume about 3GBs of RAM.
The CPU and memory usages are in burst once every hour on the
instance that does the processing.
The CPU and memory usages are in burst once every hour (or the configured periodicity) on the instance that does the processing. RAM spikes are expected to not exceed the 2GBs.
## Setup
@@ -37,13 +36,7 @@ By default, the software inventory feature is enabled and vulnerability checking
You can check to see if the software inventory feature is enabled by running the `fleetctl get config` command. If `enable_software_inventory` is set to `true`, in the command's output, the software inventory feature is already enabled.
If you disabled the software inventory feature, you must re-enable it first by setting the following environment variable:
```
FLEET_BETA_SOFTWARE_INVENTORY=1
```
Or through the app config:
If you disabled the software inventory feature, you must re-enable it first by setting the following app config:
```
---
docs/02-Deploying/02-Configuration.md
-10
View File
@@ -2077,13 +2077,3 @@ Follow these steps to configure Fleet SSO with Google Workspace. This will requi
Fleet features are sometimes gated behind feature flags. This will usually be due to not-yet-stable APIs, or not-fully-tested performance characteristics.
Feature flags on the server are controlled by environment variables prefixed with `FLEET_BETA_`.
### Software inventory
Enable by setting the environment variable `FLEET_BETA_SOFTWARE_INVENTORY=1`.
When enabled, Fleet will store a "software inventory" for hosts, updated along with the other host vitals. Note that it will take some time for the data to be available after setting this flag (it will be updated when the host details are next updated, configurable by [--osquery_detail_update_interval](#osquery-detail-update-interval)).
This is currently feature flagged because we would like to evaluate the performance characteristics on larger deployments.
To read more about the software inventory feature, [check out the Fleet 3.11.0 release blog post](https://medium.com/fleetdm/fleet-3-11-0-released-with-software-inventory-25d5a1efe19c).