What if your database admin console actually knew when to step in — caught errors on its own, and let you manage high-availability clusters in just a couple of clicks? That’s the direction we’re heading. Call it evolution.

What started as a straightforward monitoring tool, Postgres Pro Enterprise Manager (PPEM) has grown into an intelligent platform that takes the most complex and repetitive parts of a DBA’s job off your plate. In version 2.3, we’re rolling out configuration unification, proactive monitoring, and click-friendly management for built-in HA clusters — so you can finally focus on architecture, not endless ops chores.

Unification and automation

One of the biggest headaches in managing a fleet of databases is keeping configurations consistent. PPEM 2.3 tackles this with custom configuration presets. Admins can now create their own parameter sets that match internal standards, security policies, or workload profiles (say, OLTP vs. analytics). These templates can be applied to dozens of instances in minutes — saving hours of manual tuning and cutting down human error.

Alongside presets, we added bulk operations. In the Job Console, you can push a selected preset to an entire group of instances at once. The system also comes with two safety rails:

Applicability check — run a compatibility test for each instance before applying a preset.
Error limit — if failures cross a threshold, the operation stops automatically.

One important detail: with clusters (primary/replica or BiHA), order matters. If you’re adding new parameters, update replicas first, then the primary. That helps avoid replication hiccups.

Both presets and bulk ops are currently in beta and will be actively improved in upcoming releases.

From manual watching to proactive response

The Monitoring section has gone properly proactive. You can now set up triggers and alerts on key metrics. The idea is simple: define a threshold (for example, system.cpu.utilization > 90% or postgresql.archiver.failed_count > 0). When it’s hit, PPEM automatically emails the chosen users or teams.

Metrics come from PPEM’s own repository via pgpro-otel-collector, our component for collecting metrics and logs from instances. The list is broad: CPU and memory usage, deadlocks, conflicts, WAL write volume, and more. Instead of periodically asking “Is everything OK?”, you get automated control and instant incident visibility.

This is also beta for now. Today it works with metrics from pgpro-otel-collector and assumes you store metrics/logs in PPEM’s service repository.

High availability management in a few clicks

Working with BiHA (Built-in High Availability) clusters is now much easier. PPEM 2.3 turns into a real cluster control center, letting you do everything from the web UI:

create clusters from scratch or based on existing instances;
change topology — add or remove follower nodes;
perform a switchover: promote a new leader literally in two clicks.

You also get detailed replication status, including lag across stages (send → write → flush → replay). That level of visibility is crucial for diagnosing issues and keeping data consistent.

Security upgrades

Based on feedback from security teams, PPEM 2.3 brings a serious boost to access control.

Custom RBAC roles. Create your own roles with a precise set of privileges. Instead of picking only from standard system roles, you can tailor access to real job needs — for example, an auditor role that can view logs and sessions but can’t touch anything else.
Automatic user lockout. You can now block an account after a defined number of failed logins. Nothing fancy — just a must-have defense against brute-force attempts.
SSL connections to instances. The manager and agents can use SSL when connecting to database instances, so internal traffic stays encrypted.

Deeper integration

PPEM 2.3 adds two features that help it fit neatly into modern stacks:

Query tracing. We’ve added distributed tracing via OpenTelemetry (OTLP). PPEM can export trace spans to systems like Grafana Tempo or Jaeger. This makes it far easier to spot bottlenecks and debug performance in multi-service architectures.
Reverse proxy support. You can now route PPEM requests using URL prefixes, making deployment behind proxies (like Nginx) much smoother in enterprise setups.

Other notable improvements

Repository housekeeping. Automatic cleanup of service tables (old metrics, logs, etc.) on schedules and rules, preventing disk bloat.
PostgreSQL 18 support. PPEM is ready to manage the newest PostgreSQL versions.
Metric storage optimization. We redesigned the metric model into a flatter structure, reducing overhead and lowering the risk of deadlocks.

In short

Postgres Pro Enterprise Manager 2.3 isn’t just a feature drop — it’s a step toward the big goals modern IT teams care about most: automation, security, and observability. The platform is getting smarter, more flexible, and more tightly integrated into real-world workflows, so DBAs can spend less time on routine firefighting and more time solving business-level problems.

Less routine, more control: PPEM gets smarter