Select a documentation version: <button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">15.5.4</button>

- [Current (18.4.0)](https://docs.cloud.google.com/alloydb/omni/containers/current/docs/manage.md.txt)
- [18.4.0](https://docs.cloud.google.com/alloydb/omni/containers/18.4.0/docs/manage.md.txt)
- [18.3.0](https://docs.cloud.google.com/alloydb/omni/containers/18.3.0/docs/manage.md.txt)
- [18.1.0](https://docs.cloud.google.com/alloydb/omni/containers/18.1.0/docs/manage.md.txt)
- [17.10.0](https://docs.cloud.google.com/alloydb/omni/containers/17.10.0/docs/manage.md.txt)
- [17.9.0](https://docs.cloud.google.com/alloydb/omni/containers/17.9.0/docs/manage.md.txt)
- [17.7.0](https://docs.cloud.google.com/alloydb/omni/containers/17.7.0/docs/manage.md.txt)
- [17.5.0](https://docs.cloud.google.com/alloydb/omni/containers/17.5.0/docs/manage.md.txt)
- [16.14.0](https://docs.cloud.google.com/alloydb/omni/containers/16.14.0/docs/manage.md.txt)
- [16.13.0](https://docs.cloud.google.com/alloydb/omni/containers/16.13.0/docs/manage.md.txt)
- [16.11.0](https://docs.cloud.google.com/alloydb/omni/containers/16.11.0/docs/manage.md.txt)
- [16.9.0](https://docs.cloud.google.com/alloydb/omni/containers/16.9.0/docs/manage.md.txt)
- [16.8.0](https://docs.cloud.google.com/alloydb/omni/containers/16.8.0/docs/manage.md.txt)
- [16.3.0](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/manage.md.txt)
- [15.18.0](https://docs.cloud.google.com/alloydb/omni/containers/15.18.0/docs/manage.md.txt)
- [15.17.0](https://docs.cloud.google.com/alloydb/omni/containers/15.17.0/docs/manage.md.txt)
- [15.15.0](https://docs.cloud.google.com/alloydb/omni/containers/15.15.0/docs/manage.md.txt)
- [15.13.0](https://docs.cloud.google.com/alloydb/omni/containers/15.13.0/docs/manage.md.txt)
- [15.12.0](https://docs.cloud.google.com/alloydb/omni/containers/15.12.0/docs/manage.md.txt)
- [15.7.1](https://docs.cloud.google.com/alloydb/omni/containers/15.7.1/docs/manage.md.txt)
- [15.7.0](https://docs.cloud.google.com/alloydb/omni/containers/15.7.0/docs/manage.md.txt)
- [15.5.5](https://docs.cloud.google.com/alloydb/omni/containers/15.5.5/docs/manage.md.txt)
- [15.5.4](https://docs.cloud.google.com/alloydb/omni/containers/15.5.4/docs/manage.md.txt)
- [15.5.2](https://docs.cloud.google.com/alloydb/omni/containers/15.5.2/docs/manage.md.txt)

<br />

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.

<br />

## Manage user roles

AlloyDB Omni uses the same [set of predefined PostgreSQL user
roles that AlloyDB
includes](https://docs.cloud.google.com/alloydb/docs/database-users/about#psql-roles-users), 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.

As with AlloyDB, 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 user
roles](https://docs.cloud.google.com/alloydb/docs/database-users/about).

## Monitor AlloyDB Omni

Monitoring your AlloyDB Omni installation means reading and
analyzing its log files.

For a list of available metrics,
see [AlloyDB Omni metrics](https://docs.cloud.google.com/alloydb/docs/reference/omni-metrics).

### Single-server

By default, to retrieve AlloyDB Omni logs, run:

```bash
 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](https://docs.cloud.google.com/alloydb/omni/containers/15.5.4/docs/install.md.txt).

## 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](https://docs.cloud.google.com/alloydb/omni/containers/15.5.4/docs/migrate-to-latest-version.md.txt).

> [!NOTE]
> **Note:** Version 15.5.3 is a [Preview](https://cloud.google.com/products?e=48754805&#product-launch-stages) 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:

```bash
 docker container stop CONTAINER_NAME
 docker container rm CONTAINER_NAME
```

Replace `CONTAINER_NAME` with the name of your AlloyDB Omni container.

> [!CAUTION]
> **Caution:** You must [mount](https://docs.cloud.google.com/alloydb/omni/containers/15.5.4/docs/install.md.txt#mount-external-data-directory) 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.