Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

With VDG Sense 2.6.10 Postgres 13.3 is included in SenseSetup. It replaces Postgres 9.2, but does not upgrade current Postgres / database installations. New installations will use Postgres 13.3.

Key differences with previous installations are:

  • Configurable installation path, port and user credentials in SenseSetup

  • Configurable host, port and user credentials in Sense Server

Installation with postgres 9.2

If Postgres 9.2 is already installed, it will not upgrade the installation with version 13.3. In the Components page the database installation cannot be selected:

Installation with postgres 13

If the server does not have the database installed, the Components page shows the option to install the database:

In the following page the installation parameters can be configured. The username and password need to be at least 4 characters to maximum of 16 characters. It is recommended to use a complex password for the installation.

Sense configuration

After installation the server tab shows where the database connects to and the connection status itself.

A Disconnected status can occur for the following reasons:

  • Wrong user credentials

  • Wrong host or port

  • Postgres servers not running (check windows services)

To change the postgres connection or to resolve issues with user credentials, host or port, press ‘Setup Database’ button. The following dialog appears:

The following settings can be configured:

  • Host: host ip or dns name from database

  • Port: port number of database

  • Username: username of user to connect to database

  • Password: password of user to connect to database

Note: It is possible to configure a postgres host address from a postgres instance running at cloud provider like AWS, GCP or Azure.

Multi-server configuration

In all VDG Sense 2.6.9 and before the sub-servers connect to the database on the management server. This connection was automatically done by configuring the management server address on the sub servers. With VDG Sense 2.6.10 this behaviour has changed and the database configuration has to be done seperately per sub server.

IMPORTANT: If this is not done, events are NOT stored in the central / management server database. Which means they cannot be searched for as VDG Sense expects events to be stored in the central database.

  • No labels