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

Add note about async logging (#9983)

Browse Source 
Docs only change
This commit is contained in:
Katheryn Satterlee
2023-02-21 11:56:24 -06:00
committed by GitHub
parent 2e199dcdab
commit ad57147360
1 changed files with 2 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Deploying/Configuration.md
+2 -20
View File
@@ -1179,25 +1179,7 @@ osquery:
> Applies only to Fleet Premium. Acitivity information is available for all Fleet instances using the [Activities API](https://fleetdm.com/docs/using-fleet/rest-api#activities).
Stream Fleet user activities to logs using Fleet's logging plugins.
The following types of activity are included:
Created pack
Edited pack
Deleted pack
Applied pack with fleetctl
Created policy
Edited policy
Deleted policy
Applied policy with fleetctl
Created saved query
Edited saved query
Deleted saved query
Applied query with fleetctl
Ran live query
Created team
Deleted team
Stream Fleet user activities to logs using Fleet's logging plugins. The audit events are logged in an asynchronous fashion. It can take up to 5 minutes for an event to be logged.
##### activity_enable_audit_log
@@ -2998,4 +2980,4 @@ The HTTP request headers are checked in the following order:
3. If `X-Forwarded-For` header is set, then Fleet will extract the first comma-separated value.
4. If none of the above headers are present in the HTTP request then Fleet will attempt to use the remote address of the TCP connection (note that on deployments with ingress proxies the remote address seen by Fleet is the IP of the ingress proxy).
If the IP retrieved using the above heuristic belongs to a private range, then Fleet will ignore it and will not set the "Public IP address" field for the device.
If the IP retrieved using the above heuristic belongs to a private range, then Fleet will ignore it and will not set the "Public IP address" field for the device.