Hubfly spaceDocs
Console

Monitor and operate

Every instance has its own pages for watching how it runs and for changing it safely. Viewing needs the Database read permission; logs, sessions and query insights need Database query because they can show query text and data; changes need Database admin. Most changes run as an operation that you can follow step by step on the page or with hubfly db operations.

Metrics

The Metrics page shows resource use and database activity for the last 1 hour, 6 hours, 24 hours or 7 days. Samples refresh every 15 seconds while the page is open.

  • At a glance: memory use, storage use, connections in use, uptime, database size and, for PostgreSQL and MySQL, the cache hit ratio.
  • Charts: CPU as a percentage of the instance's vCPU, memory in use, network in and out, active and total connections, and throughput: transactions per second on PostgreSQL, queries per second on MySQL, statements per second on SQLite (libSQL).
bash
hubfly db metrics app-db --window 6h

Logs

The Logs page shows the database server's recent output. Hubfly space removes passwords, credentials in URLs and tokens before showing it, but logs can still include query text and data values. When the instance is stopped, its last output appears when available, which helps when it fails to start.

bash
hubfly db logs app-db
hubfly db logs app-db --follow      # keep printing new lines until Ctrl-C

Sessions

The Sessions page (PostgreSQL and MySQL) lists the open connections: user, database, client address, state, current query, duration and what the session is waiting on. It refreshes every 5 seconds. Connections whose real client address was not passed through are labelled via Hubfly space proxy; see client IP addresses. Sessions that Hubfly space itself uses are shown but cannot be stopped.

  • Cancel stops the running query. The client receives an error and the connection stays open.
  • Terminate closes the connection immediately. The client sees a disconnect and any open transaction rolls back.
bash
hubfly db sessions app-db
hubfly db sessions cancel app-db <sessionId>
hubfly db sessions terminate app-db <sessionId> --yes

Query insights

Query insights (PostgreSQL and MySQL) groups statements by shape and shows calls, total time, mean time and rows, so you can find the slowest and most frequent queries. Statistics come from pg_stat_statements on PostgreSQL and the performance schema's statement digests on MySQL; they appear once applications run queries. If they are not available yet on an instance, the page says so.

Resetting the statistics starts the counters again from zero. It does not affect the database itself.

bash
hubfly db insights app-db --order-by mean_time --limit 10
hubfly db insights reset app-db

Alerts

On the Alerts page you choose when Hubfly space warns you. Alerts appear in the Dashboard and, if you keep email on, are sent to the project's owners. They clear on their own when the condition ends.

AlertDefault
Storage used above a threshold85% (choose 50–99%)
Connections used above a threshold90% (choose 50–99%)
Instance down: the database stops answering while it should be runningOn
Email meOn

Activity and access log

  • Operations lists starts, stops, resizes, configuration changes, updates, exports and imports, with their steps, status and any error. The CLI shows the same list with hubfly db operations.
  • Access log records password reveals, credential rotations and configuration changes, with who made them.

Configuration

PostgreSQL and MySQL run with settings Hubfly space sizes for the instance. On the Configuration page you tune server settings on top of those defaults. SQLite (libSQL) has nothing to configure.

  • Settings is a searchable form of common parameters with their current value, default, allowed range and whether they need a restart. Only changed settings shows what differs from the defaults, and each one can be reset. Settings that Hubfly space manages are shown as locked.
  • Advanced lets you edit the configuration file directly (PostgreSQL postgresql.conf syntax, MySQL [mysqld] options).
  • History lists every change you applied, with its diff and optional note.

Every change goes through the same steps:

  1. Validate. Hubfly space checks the new settings against the running database: unknown or locked settings, wrong types and out-of-range values are reported, and nothing changes until they are fixed.
  2. Review. You see the diff and which settings need a restart, and can add a note about why you are changing them.
  3. Apply. Settings that can change live take effect immediately. For settings that need a restart, choose Apply now and restart, or Apply live, restart later; the instance then shows that a restart is needed to finish applying them. Apps lose their connection for a few seconds during the restart.
  4. Automatic rollback. If the new settings stop the database from starting, Hubfly space restores the previous configuration.

To undo a change, revert to an earlier revision from History. The configuration file goes back to exactly what it was in that revision; later changes are undone and the revert is recorded as a new revision. The instance must be running. If someone else changed the configuration since you loaded it, Hubfly space asks you to review the newer version instead of overwriting it.

bash
hubfly db config app-db
hubfly db config set app-db work_mem=16MB max_connections=200 --note 'more workers'
hubfly db config set app-db shared_buffers=512MB --restart now
hubfly db config history app-db
hubfly db config revert app-db <revisionId> --restart later

Start, stop and restart

  • Stop disconnects every client and keeps your data and the endpoint. A stopped instance pays for storage only.
  • Start brings it back on the same hostname and port.
  • Restart applies pending settings; apps lose their connection briefly.

If your account balance runs out, Hubfly space stops the instance and starts it again after you top up; see billing.

bash
hubfly db stop app-db
hubfly db start app-db
hubfly db restart app-db --no-wait

Resize

Open Settings and choose Resize instance to pick another preset or exact CPU and memory values, and to grow storage. The dialog shows the current and new monthly price; billing changes when the resize finishes. The instance must be running.

  • CPU and memory can go up or down, within the size limits and the engine's minimum memory.
  • Storage can grow up to 500 GiB but can never shrink.
  • Restarts. New CPU and memory limits apply without a restart. The database tunes its memory settings when it starts, so by default Hubfly space restarts it as part of the resize (Restart now to apply memory settings, or --restart in the CLI). Turn that off to restart later yourself; the instance shows a pending restart until you do. Reducing memory always restarts the database. Apps lose their connection briefly during a restart.
  • If prices changed after the quote was shown, Hubfly space refuses the resize and you get a fresh quote.
bash
hubfly db resize app-db --size medium --restart
hubfly db resize app-db --cpu 1.5 --memory 3072
hubfly db resize app-db --storage 50 --yes

Version updates

When Hubfly space publishes an update within your instance's version line (for example a new PostgreSQL 18 minor release), Settings shows it next to Database version and hubfly db info reports it. Choose Update now or run hubfly db upgrade; the instance must be running. The database is stopped, moved to the new image and started again, so apps lose their connection while it updates. Your data, hostname, port and credentials stay the same.

Updates do not change the major version. To move to another major version, create a new instance with that version and move your data with an export and import.

bash
hubfly db info app-db       # shows whether an update is available
hubfly db upgrade app-db

Rename and deletion protection

  • Rename changes the instance's display name. The hostname and connection strings stay the same.
  • Deletion protection blocks deleting the instance until it is turned off. Turn it on for production databases.
bash
hubfly db rename app-db app-db-prod
hubfly db protect app-db on

Delete an instance

Deleting is immediate and permanent: the server, its storage and all its data are removed, and there are no backups. Turn deletion protection off first, then type the instance name to confirm (or pass --yes in the CLI). When the instance is running, the delete dialog offers to start an export first; exports stay downloadable until they expire 7 days after they were created. Deleting also removes the variables that app bindings wrote.

bash
hubfly db export app-db --output app-db-final.dump
hubfly db protect app-db off
hubfly db delete app-db --wait

There is no undo

A deleted instance cannot be restored. Keep a recent export of any data you might need.
Something unclear or out of date? Emailsupport@hubfly.spaceBack to top