My Services dashboard

The My Services dashboard displays tabs according to database categories: Relational, NoSQL, and Vector databases. The Relational databases tab displays services related to your PostgreSQL database. You can filter the list by status, database engine, cloud, owner, and subscription. Users can see database services where they are granted Read-Only, Co-owner, or Owner privileges.

Dashboard filters have the following fields:

  • Search — To find and display details of a specific database service, specify the name in the search bar.

  • Total Services N — Displays the total number of listed database services, where 'N' represents the count. Next to Total Services, the following indicators are displayed:

    • A green triangle symbol with a number indicates the number of running services.

    • An orange square symbol with a number indicates the number of stopped services.

    • A grey play button symbol with a number indicates the number of starting or creating services.

    • A red cylinder with an exclamation symbol indicates the number of failed services and failed operations.

  • Engine — Choose a database engine from the dropdown list. By default, all database engine services are listed. The available options are All, MySQL, Oracle, PostgreSQL, and SQL Server.

  • Cloud — Choose a cloud provider from the dropdown list. By default, all cloud providers are listed. The available options are All, AWS, Azure, and GCP.

  • Owner — Choose a specific username from the dropdown list to view database services specific to that user. By default, all services shared with you are listed.

  • Subscription — Choose a specific subscription from the dropdown list. By default, all subscriptions added to your account are listed if you are the account owner.

The Relational databases table displays the following columns:

Service Name — Displays the name you assigned to the database service during provisioning, along with the PostgreSQL engine icon. Clicking the service name directs you to its dedicated home page.

Status — Displays the current status of your database service. A specific number of dots in the status field represents the number of instances that are part of the database service.

  • One dot: Single-node database service with one instance.

  • Two dots: Two-node database service with two instances (one primary, one replica). The replica can be an HA, DR, or Read Replica instance.

  • Three dots: Three-node database service with three instances (one primary, two replicas), and so on.

The status of your database service can be as follows:

Status
Description
Actions allowed

Ready

Database service is created and running. Connections are allowed after the service reaches Ready status.

All actions are allowed:

  • Stop the service

  • Edit the service

  • Restore the service

  • Resize the compute shapes

  • Resize the storage

  • Update the parameter profile

  • Reset the password

  • Modify public accessibility, allowed IP addresses, AWS private link, and Tags

  • Switch over to a replica

  • Add new databases

  • Delete existing databases

  • Enable third-party integrations

  • Set or modify Start/Stop schedules

  • Share the service with users

Starting

Database service is in the process of starting. Connections are not allowed while the service is starting.

Edit the service

Stopping

Database service stop is triggered and the stopping process is in progress. All connections and the database service are stopped.

Edit the service

Stopped

Database service is not running.

Start the service

Down

Primary instance in the High Availability service or the single instance is down. This indicates unplanned downtime.

Start the instance

Deleting

Database service delete is triggered and the deletion process is in progress.

No actions allowed

Creating

Database service provision is triggered and the creation process is in progress.

No actions allowed

Failed

Database service provision or restore operation failed.

Clean up the database service entry using the remove button. A failed entry is automatically cleaned up after 60 minutes.

Rebuilding

Compute shape resize or storage resize is running on the database service.

No actions allowed

Under_maintenance

Database maintenance activity is in progress as per the scheduled maintenance window.

  • Delete the service

  • Restore the service

  • Resize the compute shape

  • Resize the storage size

  • Update the parameter profile

  • Reset the password

  • Modify public accessibility, allowed IP addresses, AWS private link, and Tags

  • Switch over to a replica

  • Add new databases

  • Delete existing databases

  • Set or modify Start/Stop schedules

  • Share the service with users

Switching

Replica in the High Availability service is being promoted as the primary instance.

No actions allowed

Degraded

One of the replica instances in the High Availability service is down.

  • Delete the service

  • Edit the service

  • Restore the service

  • Resize the compute shape

  • Resize the storage size

  • Update the parameter profile

  • Reset the password

  • Modify public accessibility, allowed IP addresses, AWS private link, and Tags

  • Switch over to a replica

  • Add new databases

  • Delete existing databases

  • Enable third-party integrations

  • Set or modify Start/Stop schedules

  • Share the service with users

Healing

Tessell platform has detected unplanned downtime in one or more instances and is attempting to auto-heal.

No actions allowed

Patching

Available patches are selected and being applied.

No actions allowed

Updating

Parameter profile is being updated for one or more instances in the database service.

No actions allowed

Parameter_profile_update_failed

Parameter profile update failed but the database service is Ready.

All actions are allowed

Rebuild_failed

Compute resize or storage resize did not complete but the database service is Ready.

All actions are allowed

Backing_up

Snapshot is running.

Edit the service

Start_failed

Database service restart failed.

Start the service

Stop_failed

Database service stop failed.

All actions are allowed

Switch_over_failed

Switch over operation for a High Availability database service failed.

All actions are allowed

Note: For all failed operations, raise a ticket to Tessell support through the Report a problem option.

Subscription — Displays the subscription you chose during provisioning. You can define and add subscriptions using the Subscriptions app under the Governance app family.

Infrastructure — Displays the compute shape you chose for your database service during provisioning.

Cloud and Region — Displays the cloud and region name you chose to host your database service during provisioning.

Created On — Displays the creation date and time of your database service.

Created By — Displays the username used to log in to the Tessell portal and create the database service.

Figure 1: My Services dashboard

Last updated

Was this helpful?