Manage and monitor AlloyDB Omni

Select a documentation version: Current (16.8.0)

• Current (16.8.0)
• 16.8.0
• 16.3.0
• 15.12.0
• 15.7.1
• 15.7.0
• 15.5.5
• 15.5.4
• 15.5.2

This page describes how to manage AlloyDB Omni user roles, monitor the activity of your AlloyDB Omni server, and update or remove your AlloyDB Omni installation.

Manage user roles

AlloyDB Omni uses the same set of predefined PostgreSQL user roles that AlloyDB for PostgreSQL includes, with the following differences:

• AlloyDB Omni includes a superuser role named alloydbadmin, and a non-superuser role named alloydbmetadata.

• The default postgres user has a superuser role.

• All other predefined user roles have no privileges. They are reserved for potential uses in the future.

Set up an AlloyDB Omni database

As with AlloyDB for PostgreSQL, it's a best practice to follow these steps when setting up a database:

1. Define or import your databases using the postgres user role. In a new installation, this role has superuser privileges, and requires no password.

2. Create new user roles that have the correct level of access to your application's tables, again using the postgres user role.

3. Configure your application to connect to the database using these new, limited-access roles.

You can create and define as many new user roles as you need. Don't modify or delete any of the user roles with which AlloyDB Omni ships.

For more information, see Manage AlloyDB Omni users and roles.

Monitor AlloyDB Omni

Monitoring your AlloyDB Omni installation includes reading and analyzing AlloyDB Omni log files.

For a list of available metrics, see AlloyDB Omni metrics.

Single-server

By default, to retrieve AlloyDB Omni logs, run:

Docker

  docker logs CONTAINER_NAME

Replace CONTAINER_NAME with the name of your AlloyDB Omni container.

To configure the logging behavior of AlloyDB Omni, see Customize your AlloyDB Omni installation.

Podman

  podman logs CONTAINER_NAME

Replace CONTAINER_NAME with the name of your AlloyDB Omni container.

To configure the logging behavior of AlloyDB Omni, see Customize your AlloyDB Omni installation.

Upgrade AlloyDB Omni

To upgrade from AlloyDB Omni 15.5.2 or earlier to 15.5.4, follow instructions in Migrate from earlier version of AlloyDB Omni to latest version.

Note: Version 15.5.3 is a Preview version of AlloyDB Omni.

To upgrade from 15.5.4 and later:

1. Restart AlloyDB Omni using a new image version.

2. Make sure to specify your data directory to match the same path as used in earlier versions of AlloyDB Omni.

Uninstall AlloyDB Omni

Single-server

To uninstall AlloyDB Omni, stop and delete the AlloyDB Omni container using the following command:

Docker

 docker container stop CONTAINER_NAME
   docker container rm CONTAINER_NAME

Replace CONTAINER_NAME with the name of your AlloyDB Omni container.

Caution: You must mount an external data directory, so that your database data is not deleted when you delete the container.

Podman

 podman container stop CONTAINER_NAME
   podman container rm CONTAINER_NAME

Replace CONTAINER_NAME with the name of your AlloyDB Omni container.

Caution: You must mount an external data directory, so that your database data is not deleted when you delete the container.

Podman

 podman container stop CONTAINER_NAME
   podman container rm CONTAINER_NAME

Replace CONTAINER_NAME with the name of your AlloyDB Omni container.

Caution: You must mount an external data directory, so that your database data is not deleted when you delete the container.

You can move, archive, or delete an external data directory depending on whether and how you want to preserve your data after uninstalling AlloyDB Omni.