mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 00:49:03 +00:00
Moving to deployment FAQ
This commit is contained in:
parent
f1f68273bd
commit
f34bab62c8
1 changed files with 0 additions and 4 deletions
|
|
@ -186,7 +186,3 @@ Yes, Orbit can be run alongside osquery. The osquery instance that Orbit runs us
|
|||
## What happens to osquery logs if my Fleet server or my logging destination is offline?
|
||||
|
||||
If Fleet can't send logs to the destination, it will return an error to osquery. This causes osquery to retry sending the logs. The logs will then be stored in osquery's internal buffer until they are sent successfully, or they get expired if the `buffered_log_max`(defaults to 1,000,000 logs) is exceeded. Check out the [Remote logging buffering section](https://osquery.readthedocs.io/en/latest/deployment/remote/#remote-logging-buffering) on the osquery docs for more on this behavior.
|
||||
|
||||
## What API endpoints should I expose to the public internet?
|
||||
|
||||
If you would like to manage hosts that can travel outside your VPN or intranet we recommend only exposing the "/api/v1/osquery" endpoint to the public internet.
|
||||
|
|
|
|||
Loading…
Reference in a new issue