![]() In that case the options are the same, except that the YAML section is mysql_read_replica, and the flags have the mysql_read_replica_ prefix instead of mysql_ (the corresponding environment variables follow the same transformation). Suppose you also want to set up a read replica. This section describes the configuration options for the primary. The conversion works the same the opposite way.Īll duration-based settings accept valid time units of s, m, h. ![]() Further, specifying the mysql_address option in the config would follow the pattern: mysql:Īnd mysql_read_replica_address would be: mysql_read_replica:īasically, just capitalize the option and prepend FLEET_ to it to get the environment variable. For example, the -mysql_address flag would be the FLEET_MYSQL_ADDRESS. Note that all option names can be converted consistently from flag name to environment variable and visa-versa. Using only CLI flags /usr/bin/fleet serve \ Using only environment variables FLEET_MYSQL_ADDRESS=127.0.0.1:3306 \ģ. Using a YAML config file echo 'įor more information on using YAML configuration files with fleet, please see the configuration files documentation. You can specify options in the order of precedence viaįor example, all of the following ways of launching Fleet are equivalent: 1. The fleet binary contains several "commands." Similarly to how git has many commands ( git status, git commit, etc.), the fleet binary accepts the following commands: Various details about the refresh/check-in intervals for your hosts.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. Configuration Configuring the Fleet binaryįor information on how to run the fleet binary, find detailed usage information by running fleet -help. ![]()
0 Comments
Leave a Reply. |