Skip to content

Settings and preferences

For the complete documentation index see: llms.txt

All documentation pages available in markdown.

Aerospike Voyager preferences are organized into three tabs: General, Security & privacy, and Advanced. Open Preferences from the gear icon at the bottom of the sidebar.

Settings hold values that apply to Voyager as a whole. To change how Voyager reads, writes, queries, or connects to one particular cluster, see Tuning Voyager behavior.

Prerequisites

General

The General tab covers application behavior. On the desktop application it also shows a Software updates card, which holds the current version, an Auto-check for updates toggle, and a Check now button.

Preferences General tab with the Application card showing the Show update notifications toggle and Default records per page set to 25

Application

SettingDefaultDescription
Show update notificationsOnDisplay a notification when a new version is available.
Default records per page25Number of records displayed per page in the data browser (range: 1-50).

Security & privacy

The Security & privacy tab covers telemetry.

Telemetry

SettingDefaultDescription
Usage analyticsOnSend anonymous usage statistics to help improve Voyager. You can opt out at any time.

See Telemetry for the complete list of what is collected, what is not collected, and how the anonymous identifier works.

Opting out

Toggle Usage analytics off at any time:

  • First launch: toggle it off on the Privacy settings screen before clicking Get started. If you do, no telemetry is collected at all.
  • After first launch: open Preferences > Security & privacy and toggle Usage analytics off. The change takes effect immediately.

Advanced

The Advanced tab covers global connection defaults and developer options.

Preferences Advanced tab with the Connection settings card showing Connection timeout at 30 seconds, the Use services alternate toggle, Info timeout at 2000 ms, and a collapsed Advanced options toggle, above Developer options

Connection settings

Connection settings holds the connect and info policy defaults Voyager uses when dialing any cluster. Changes take effect the next time a connection connects or reconnects.

SettingDefaultDescription
Connection timeout30 secondsTime to wait before a connection attempt is considered failed. Enter a value from 1 to 3600 seconds. Setting a timeout on an individual connection overrides this default.
Use services alternateOffUse the services-alternate addresses advertised during cluster tend, for cloud and Kubernetes deployments. A value set on the connection itself overrides this default.
Info timeout2000 msSocket timeout for cluster info commands.

Expand Advanced options for the remaining connect policy fields, including login timeout, cluster name, tend and config intervals, connection pool sizing, circuit-breaker thresholds, and rack awareness.

Per-connection overrides win over these defaults. To set a value for one cluster only, and to reach the read, write, and query policies, see Tuning Voyager behavior. That guide documents every field with its unit, default, and valid range.

Developer options

SettingDefaultDescription
Enable debug loggingOffWrite detailed diagnostic information to a log file. Enable this when reporting issues.

Reset to defaults

Click Reset to defaults in the Developer options section to restore Voyager to its initial state. This action:

  • Deletes all saved connections
  • Resets all preferences to defaults
  • Revokes any MCP tokens

MCP tool profile

The MCP tool profile is configured on the MCP Server page, not in Settings. See Access profiles for the available profiles and what each one exposes.

Next steps