Supported databases

Overview Copied

Opsview Monitor is compatible with MySQL and MariaDB, as listed in its Supported databases.

Note

Starting with Opsview 6.10.0, only the database client or server versions included with the default and non-default database options for each supported operating system are supported.

Supported databases Copied

Opsview Monitor installs and supports the following database vendors and versions (client and server). The specific database supported depends on the operating system of the orchestrator system or the deploy-managed remote database server.

Note

All testing is performed with database client and database server having the same vendor and version. Mixing and matching vendors and versions is not supported.

Local database server Copied

Default database Copied

To use the default database, no additional configuration is required. The default database is installed and configured automatically. Using user_vars.yml to configure database settings is not supported for the default database option.

Non-default database Copied

To use a non-default database option for a particular OS, add the following configuration to the user_vars.yml file before installing via the Advanced Automated Installation page.

opsview_database_package_vendor: <mariadb|mysql>
opsview_database_package_version: <version>

For example, to use a non-default database option of MariaDB 10.6 on Ubuntu 22:

opsview_database_package_vendor: 'mariadb'
opsview_database_package_version: '10.6'

Remote database servers Copied

Remote database servers must run a supported version based on the list of supported databases. Furthermore, the vendor and version of the database server must match the orchestrator. These constraints apply to both deploy-managed and unmanaged remote database servers.

For deploy-managed remote database servers, follow the local database server guidance on default database and non-default database options during installation.

Amazon RDS Copied

Opsview Monitor also supports Amazon RDS. However, the selected database must align with our supported database policy for the orchestrator’s operating system.

Examples Copied

Opsview supports various use case scenarios involving different operating systems and databases. As long as the selected database configuration adheres to our established database policy, it will be considered supported.

Examples:

• An Opsview orchestrator deployed on Ubuntu 20 without a remote database server will use MySQL 8 locally for both client and server functions by default.
• An Opsview orchestrator deployed on Ubuntu 20 without a remote database server can use MariaDB 10.5 locally for both client and server functions if configured to use a non-default database option.
• For an Opsview orchestrator deployed on OL 9 using a deploy-managed remote database server, the remote database server must be running MariaDB 10.5. This ensures it matches the MariaDB 10.5 client on the orchestrator.
• An Opsview orchestrator deployed on Debian 10 using an unmanaged remote database server requires a remote database server running MariaDB 10.3. This ensures that the MariaDB 10.3 client on the orchestrator matches the server version.