These are the currently known issues and limitations identified in the WarehousePG Enterprise Manager (WEM) release. Where applicable, we've included workarounds to help you mitigate the impact of these issues. These issues are actively tracked and are planned for resolution in a future release.
Deployment & infrastructure
- Each WEM deployment is designed to manage and monitor only one WarehousePG (WHPG) cluster. Managing multiple clusters requires separate, dedicated WEM installations for each.
- WEM can't be installed on Red Hat Enterprise Linux 7. However WEM is fully capable of monitoring WHPG 6.x clusters running on RHEL 7 nodes.
Disaster recovery
- Safeguard supports only one storage repository and only one DR cluster at a time. Managing multiple DR standbys or storage backends from the same WEM install isn't supported.
Query monitoring
- The Query Editor supports running
EXPLAINon queries you write, but WEM doesn't capture execution plans for queries that are already running. To investigate the plan of an in-flight query, connect to the cluster directly usingpsqland runEXPLAINagainst the query text.
Alerting
- WEM doesn't offer a form-based interface for configuring notification receivers, such as email, Slack, or PagerDuty. Edit Alertmanager's own configuration directly instead, using the raw YAML editor on the Notifications tab. See Alertmanager notification configuration for the YAML syntax.
- Upgrading to 1.4 deletes existing User alert rules rather than migrating them, since Prometheus, where they're stored, is removed as part of the upgrade. System rules are recreated automatically using ClickHouse SQL, and alert history is preserved regardless of which engine originally raised it. Note down any User alert rules before upgrading and recreate them afterward through the Rules tab. See Upgrading WarehousePG Enterprise Manager.