Manage Servers
The Servers page lists all registered PostgreSQL servers and provides actions to manage their monitoring state.
Accessing the Servers List
Navigate to Servers in the main navigation bar.
{screenshot: servers-list-page}
The list displays for each server:
| Column | Description |
|---|---|
| Hostname | Server display name |
| Host / Port | PostgreSQL connection address |
| Environment | RUN or BUILD |
| Version | PostgreSQL version |
| Status | ACTIVE, INACTIVE, ERROR, DISABLED, MAINTENANCE |
| Last Heartbeat | Time of the last agent heartbeat |
| Actions | Context menu with available operations |
Server Statuses
| Status | Meaning |
|---|---|
| ACTIVE | Agent is running and sending data normally |
| INACTIVE | No heartbeat received recently — agent may be down |
| ERROR | Agent reported an error connecting to PostgreSQL |
| DISABLED | Server manually disabled by an administrator |
| MAINTENANCE | Server placed in maintenance mode — alerts suppressed |
Available Actions
Click the ⋮ (actions menu) on any server row to access the following actions:
{screenshot: server-actions-menu}
View Details
Opens the Server Detail → page for the selected server. This is also triggered by clicking anywhere on the server row.
Disable / Enable
Disable a server to pause monitoring without deleting it from the platform. When disabled:
- The agent continues running on the server side
- The backend ignores incoming metrics from this agent
- The server appears with status DISABLED in the dashboard
- No new alerts are generated for this server
Enable restores normal monitoring for a previously disabled server.
{screenshot: disable-server-confirmation}
:::tip Use case Disable a server before a planned maintenance window to avoid alert noise, then re-enable it once maintenance is complete. :::
Delete
Permanently removes the server and its agent record from the platform.
{screenshot: delete-server-confirmation}
Deleting a server removes all reference data for that server from the platform. Historical metrics stored in *_history tables are also removed. This action cannot be undone.
Before deleting, stop the agent service on the target server to prevent it from attempting to send metrics with an invalidated API key.
Bulk Operations
Currently, actions must be performed on one server at a time. Bulk operations are planned for a future release.