When installing Axoflow agent on Windows, you can set a number of advanced options if needed for your environment. Setting the advanced options in the Axoflow Console automatically updates the one-liner command that you can copy and run.
Alternatively, before running the one-liner you can use one of the following methods:
-
Set the related environment variable for the option. For example:
$Env:AXOLET_INITIAL_LABELS = 'product=windows,team=windows,vendor=microsoft'
-
Set the related URL parameter for the option. For example:
curl.exe -fLsH 'X-AXO-TOKEN:random-generated' 'https://<your-tenant-id>.cloud.axoflow.io/setup.sh?type=AXOEDGE&platform=WINDOWS&initial_labels=product%3Dwindows%2Cvendor%3Dmicrosoft%2Cteam%3Dwindows' -o $env:TEMP\axolet-installer.ps1; powershell.exe -File $env:TEMP\axolet-installer.ps1
Proxy settings
Use the HTTP proxy, HTTPS proxy, No proxy parameters to configure HTTP proxy settings for the installer. To avoid using the proxy for the Axolet service, enable the Avoid proxy parameter as well. Lowercase variable names are preferred because they work universally.
Installation options
You can pass the following parameters to the installation script as environment variables, or as URL parameters.
API server host
Default value: | |
Environment variable | |
URL parameter | api_server_host |
Description: Override the host part of the API endpoint for the host.
Avoid proxy
Default value: | false |
Available values: | true , false |
Environment variable | AXOLET_AVOID_PROXY |
URL parameter | avoid_proxy |
Description: If set to true
, the value of the *_proxy
variables will only be used for downloading the installer, but not for the axolet
service itself. If set to false
, the Axolet service will use the variables from the installer.
Collector agent URL
Default value: | https://github.com/axoflow/axoflow-otel-collector-releases/releases/download/v<version-number>/axoflow-otel-collector_<version-number>_windows_x64.msi |
Environment variable | AXOLET_COLLECTOR_AGENT_URL |
URL parameter | collector_agent_url |
Description: Deploy the specified agent binary.
Configuration directory
Default value: |
C:\ProgramData\Axoflow
|
Environment variable | AXOLET_CONFIG_DIR |
URL parameter | config_dir |
Description: The directory where the configuration files are stored.
HTTP proxy
Default value: | empty string |
Environment variable | AXOLET_HTTP_PROXY |
URL parameter | http_proxy |
Description: Use a proxy to access Axoflow Console from the host.
HTTPS proxy
Default value: | empty string |
Environment variable | AXOLET_HTTPS_PROXY |
URL parameter | https_proxy |
Description: Use a proxy to access Axoflow Console from the host.
Initial labels
Default value: | empty string |
Environment variable | AXOLET_INITIAL_LABELS |
URL parameter | initial_labels |
Description: Comma-separated list of key=value
labels. These labels will be suggested for the host when you add the source to Axoflow Console. For example, product=windows,team=windows,vendor=microsoft
No proxy
Default value: | empty string |
Environment variable | AXOLET_NO_PROXY |
URL parameter | no_proxy |
Description: Destinations that should be reached directly, without going through the proxy.
Overwrite config
Default value: | false |
Available values: | true , false |
Environment variable | AXOLET_CONFIG_OVERWRITE |
URL parameter | config_overwrite |
Description: If set to true
, the configuration process will overwrite existing configuration (/etc/axolet/config.json
). This means that the agent will get a new GUID and it will require approval on the Axoflow Console.
Start service
Default value: | AXOLET_START=true |
Available values: | true , false |
Environment variable | AXOLET_START |
URL parameter | start |
Description: Start axolet agent at the end of installation. Use false for preparing golden images. In this case axolet
will generate a new GUID on the first boot after cloning the image.
If you are preparing a host for cloning with Axolet already installed, set the following environment variable in your (root) shell session, before running the one-liner command. For example:
$Env:START_AXOLET = false
curl.exe ... # Run the command copied from the Provisioning page
This way Axolet will only start and initialize after the first reboot.