Configure Oso Fallback
You must configure the following environment variables to start the Oso Fallback node:
| Environment Variable | Description |
|---|---|
OSO_API_TOKEN | Read-only API key for the desired environment. You may create a new API key by following this guide. |
OSO_ENVIRONMENT | ID of the desired environment. You may find the ID of the environment on the Environments page (opens in a new tab). |
OSO_TENANT | ID of the tenant where the environment resides. You may find the ID of the tenant at the top of the Settings page (opens in a new tab). |
Additional environment variables you may configure include:
| Environment Variable | Default | Accepted Values | Description |
|---|---|---|---|
OSO_CLIENT_ID | Randomly generated UUID | String containing the following characters: a-zA-Z0-9.- | Unique identifier for each Oso Fallback node. You may want to use this value to tie connected clients in the Fallback status page (opens in a new tab) to the underlying infrastructure. If not set, a randomly generated UUID is used. If set, the OSO_CLIENT_ID must be unique per restart or redeployment. |
OSO_DISABLE_ERROR_LOGGING | false | true, false | Whether error logs are sent to Oso's error collector for review and analysis. |
OSO_DISABLE_TELEMETRY | false | true, false | Whether usage data are sent to Oso's telemetry collector for review and analysis. |
OSO_LOG_LEVEL | error | info, warn, error | Verbosity of log messages printed to stdout. |
OSO_PORT | 8080 | 0 to 65535 | Port for the Oso Fallback node to listen on. |
OSO_DIRECTORY | ./.oso | String containing a valid path | Path where the Fallback node stores data. |