Monitoring in Console

The Monitoring section turns Console into more than just a control panel. It is a real operating tool. Here you can see not only the administrative state of a resource, but also the actual behavior of the database.

Metrics

The Metrics tab shows key database indicators over time. Usually these include:

• CPU;
• memory;
• database size;
• connections;
• deadlocks;
• other operational metrics, if available in the current environment.

Metrics are especially useful:

• after a release;
• when users complain about performance;
• when you suspect connection leaks;
• when you want to check whether the database is actually in use.

Logs

Logs is a live stream of PostgreSQL / compute logs for the selected database. In Console, it usually provides:

• live tail;
• pause and resume;
• substring filtering;
• time-range selection;
• buffer copy;
• log export.

A practical pattern is very simple: reproduce the issue in the application and immediately look at which log line appeared at the same moment.

Active queries

The Active queries tab helps you understand what is running right now. It usually shows:

• pid;
• query state;
• duration;
• waits and locks;
• user;
• SQL text.

This is useful for finding long-running queries, stuck operations, and the real reasons behind “the database feels slow.”

In some Console builds, operator actions such as cancel / terminate are available. Use them carefully, understanding the impact on the application.

Query statistics / Performance

This tab shows the overall picture of SQL workload: number of calls, total and average time, and the query text. It is especially useful for optimization and for finding “expensive” SQL patterns.

Keep in mind that this section depends on statistics availability on the PostgreSQL side: if the required extension is not enabled, there may be no data.

Operations

The Operations tab shows operations initiated through the UI for the selected database: creation, deletion, success, or failure. It is a working history of actions, not a full audit log of the whole platform.

What is important to remember

• for a stopped database, some monitoring data may be unavailable;
• empty graphs or logs do not always mean a malfunction — sometimes the corresponding backend is simply not active;
• Monitoring is your first diagnostic tool before contacting support.

It is precisely the combination of metrics, logs, active queries, and operation history that makes SPG99 transparent and fast to operate for the user.