The destination of the osquery status and result logs on the local filesystem.Since Fleet is an osquery TLS server, you are also able to define configurations that can customize your experience there, such as: When deploying Fleet, mitigate DoS attacks as you would when deploying any app. The TLS certificates that Fleet should use to terminate TLS.Since Fleet is a web application, when you run it there are other configurations that must be defined, such as: Thus, Fleet also requires that you supply Redis connection configurations.įleet can scale to hundreds of thousands of devices with a single Redis instance and is also compatible with Redis Cluster. Fleet also uses Redis to perform more high-speed data access action throughout the applications lifecycle (for example, distributed query result ingestion). It is also possible to configure your connection to a MySQL replica in addition to the primary. Fleet uses MySQL and requires you to supply configurations to connect to a MySQL server. The Fleet server allows you to persist configuration, manage users, etc. To serve the Fleet web UI, which allows you to manage osquery configuration, query hosts, etc.Your Fleet server's two main purposes are: In order to get the most out of running the Fleet server, it is helpful to establish a mutual understanding of what the desired architecture looks like and what it's trying to accomplish. If you prefer to use a CLI instead of a web browser, we hope you like the binary interface of the Fleet application! High-level configuration overview This document is a more detailed version of the data presented in the help output text.
#Osquery prometheus how to
Configuration Configuring the Fleet binaryįor information on how to run the fleet binary, find detailed usage information by running fleet -help.
0 kommentar(er)
