Changes

mpfuster · mpfuster · commit cd1dbd8869f4 · 2026-03-02T22:10:39.000Z
diff --git a/advocacy_docs/supported-open-source/warehousepg/index.mdx b/advocacy_docs/supported-open-source/warehousepg/index.mdx
@@ -7,6 +7,7 @@ navigation:
 - observability
 - flowserver
 - whpg-copy
+- wem
 directoryDefaults:
     iconName: BigData
 ---
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/get-started.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/get-started.mdx
@@ -19,34 +19,34 @@ To begin managing your cluster:
 
 For security, sessions automatically expire after a period of inactivity; if a timeout occurs, the system will display a "Session Expired" message and redirect you to the login screen. You can also manually terminate your session at any time by selecting the **Logout** icon located in the sidebar footer.
 
-## Configuring WEM settings
-
-Once you have installed WEM, you can fine-tune how WEM connects to your cluster or configure other external services (Prometheus and Alertmanager) using two methods:
 
-1. **Method 1: Use the WEM settings tab**
-
-    Administrators can modify most operational parameters directly through the browser:
-    1. Navigate to **User Management** > **Settings**.
-    1. Update fields such as **Prometheus URL** or **Backup History Database Path**.
-    1. Save to apply changes immediately.
+## Navigating the interface structure
 
-!!! Note
-    Some low-level system parameters are only accessible via the configuration file.
+The WEM interface is organized into the following functional areas:
+1. **Panels (left sidebar):**  The primary functional modules (e.g., **Cluster**, **Monitoring**, **Access Management**).
+1. **Header (top):** View the current page title, system time, and global controls (filters and refresh triggers).
+1. **Tabs (top of content):** Specific tools or sub-views within a selected panel.
+1. **Main content (center):** Interact with data tables, performance charts, and configuration tools.
 
-2. **Method 2: Edit the configuration file manually**
+**Navigation directory**
 
-    For low-level system parameters not exposed in the WEM console, or for automated deployments, edit the WEM configuration file directly on the host server:
-    1. Stop the service: `systemctl stop wem` on the WEM host.
-    1. Edit the file `/etc/wem/wem.conf` and modify the desired parameter.
-    1. Restart the service: `systemctl start wem`.
+Use the following guide to locate specific tools and their corresponding documentation:
 
+| Panel (sidebar) | Key actions |
+| --------------- | ------------ |
+| Cluster | [Verifying the cluster health](monitoring/cluster-overview/) |
+| Query Monitor | [Monitoring and evaluating queries](performance/query-monitor/) |
+| Data Analysis | [Analyzing data distribution](performance/data-analysis/) |
+| Storage | [Planning storage capacity](performance/storage/) |
+| Access Management | [Defining access policies](system-access/access-management/) |
+| System Metrics | [Visualizing hardware performance](monitoring/system-metrics/) |
+| Resource Management | [Managing system resources](performance/managing-resources/) |
+| Backups | [Securing backups](performance/backups/) |
+| Logs | [Auditing system logs](monitoring/logs/) |
+| Monitoring | [Validating database responsiveness](monitoring/monitoring/) |
+| Alerts | [Managing alerts](monitoring/alerts/) |
+| User Management | [Provisioning user accounts](system-access/user-management/)
 
-## Navigating the interface structure
-
-The WEM interface is organized into three functional areas:
-1. **Sidebar (left):** Access all primary tabs, including the **Query Monitor**, **Backups**, and **Data Analysis**.
-1. **Header (top):** View the current page title, system time, and global controls (filters and refresh triggers).
-1. **Main content (center):** Interact with data tables, performance charts, and configuration tools.
 
 ## Understanding user roles and permissions
 
@@ -87,6 +87,26 @@ WEM streams live data into three primary charts:
 
 Review the **Recent WHPG Log Alerts** card for WHPG log events. Open the **Logs** panel for a full audit trail.
 
+## Configuring WEM settings
+
+Once you have installed WEM, you can fine-tune how WEM connects to your cluster or configure other external services (Prometheus and Alertmanager) using two methods:
+
+1. **Method 1: Use the WEM settings tab**
+
+    Administrators can modify most operational parameters directly through the browser:
+    1. Navigate to **User Management** > **Settings**.
+    1. Update fields such as **Prometheus URL** or **Backup History Database Path**.
+    1. Save to apply changes immediately.
+
+!!! Note
+    Some low-level system parameters are only accessible via the configuration file.
+
+2. **Method 2: Edit the configuration file manually**
+
+    For low-level system parameters not exposed in the WEM console, or for automated deployments, edit the WEM configuration file directly on the host server:
+    1. Stop the service: `systemctl stop wem` on the WEM host.
+    1. Edit the file `/etc/wem/wem.conf` and modify the desired parameter.
+    1. Restart the service: `systemctl start wem`.
 
 
 
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/index.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/index.mdx
@@ -8,7 +8,7 @@ navigation:
 - get-started
 - monitoring
 - performance
-- security
+- system-access
 - troubleshooting
 - reference
 navRootedTo: /supported-open-source/warehousepg/
@@ -54,4 +54,4 @@ WEM introduces a robust suite of tools for the modern database administrator and
 - **Data protection**
     - **Backup & recovery:** Centralized monitoring of backup schedules, recovery points, and success rates.
 
-    - ***Canary checks:** Automated "heartbeat" tests that proactively verify cluster connectivity and query responsiveness.
+    - **Canary checks:** Automated "heartbeat" tests that proactively verify cluster connectivity and query responsiveness.
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/installing/wem.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/installing/wem.mdx
@@ -53,8 +53,13 @@ Edit the configuration file `/etc/wem/wem.conf` and configure the following para
 
 1. To enable centralized alert handling and notifications with Alertmanager, configure the `ALERTMANAGER_URL` parameter to point to your Alertmanager endpoint.
 
-1. Optionally, set the parameters `WEM_EXPORTER_LOG_LEVEL`, `WEM_EXPORTER_REMOTE_WRITE_INTERVAL`, and `WEM_EXPORTER_REMOTE_WRITE_TIMEOUT` for advanced configuration settings.
+1. Optionally, configure advanced settings to fine-tune logging and data transmission:
 
+    - `WEM_EXPORTER_LOG_LEVEL`: Sets the verbosity of the Exporter logs ((`debug`, `info`, `warn`, or `error`)) to assist with troubleshooting.
+
+    - `WEM_EXPORTER_REMOTE_WRITE_INTERVAL`: Defines how frequently (e.g., 15s, 1m, 5m) the Exporter pushes collected metrics to the remote storage.
+
+    - `WEM_EXPORTER_REMOTE_WRITE_TIMEOUT`: Specifies the maximum time (e.g., 30s, 1m, 2m) allowed for a data push to complete before the attempt is considered a failure.
 
 ### Configuring WEM portal access
 
@@ -123,9 +128,16 @@ After starting the service, use these diagnostic tools to ensure all WEM compone
 ```bash
 wem setup --verify
 ```
+See [wem setup command reference](../reference/commands#wem-setup) for details.
 
 - Perform a comprehensive "doctor" check to identify potential configuration errors, missing dependencies, or connectivity issues:
 
 ```bash
 wem doctor
 ```
+
+See [wem doctor command reference](../reference/commands#wem-doctor) for details.
+
+
+!!! Note Post-installation changes: 
+    If you need to modify your environment after the initial setup, refer to the [Configuring WEM settings](../get-started#configuring-wem-settings) section for the appropriate procedures and requirements.
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/alerts.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/alerts.mdx
@@ -5,7 +5,7 @@ description: Use the Alerts panel to integrate with Prometheus Alertmanager and
 deepToC: true
 ---
 
-The **Alerts** panel serves as the central nervous system for your cluster, aggregating health signals from across your infrastructure. This panel integrates directly with Prometheus Alertmanager to provide a unified interface for incident response and rule management.
+The **Alerts** panel on the left sidebar serves as the central nervous system for your cluster, aggregating health signals from across your infrastructure. This panel integrates directly with Prometheus Alertmanager to provide a unified interface for incident response and rule management.
 
 !!! Warning "Alertmanager required"
     If the **Alerts** panel displays `Alertmanager Not Configured`, you must set the `ALERTMANAGER_URL` in your system environment. See [Configuring WEM](../installing/wem#configuring-wem) and [Configuring WEM settings post-installation](../get-started#configuring-wem-settings) for details.
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/cluster-overview.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/cluster-overview.mdx
@@ -5,7 +5,7 @@ description: Use the Cluster Overview panel to monitor real-time WarehousePG clu
 deepToC: true
 ---
 
-The **Cluster** panel provides a high-level summary of the WarehousePG (WHPG) cluster configuration and real-time health metrics. This panel is the primary starting point for verifying cluster availability and resource utilization.
+The **Cluster** panel on the left sidebar provides a high-level summary of the WarehousePG (WHPG) cluster configuration and real-time health metrics. This panel is the primary starting point for verifying cluster availability and resource utilization.
 
 ### Confirming core cluster availability
 
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/logs.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/logs.mdx
@@ -5,7 +5,7 @@ description: Use the Log panel to access, filter, and analyze system and databas
 deepToC: true
 ---
 
-The **Logs** panel serves as a centralized diagnostic hub. By consolidating internal database metrics with external log aggregation, it allows you to correlate system-level events with specific query failures.
+The **Logs** panel on the left sidebar serves as a centralized diagnostic hub. By consolidating internal database metrics with external log aggregation, it allows you to correlate system-level events with specific query failures.
 
 ### Understanding log levels
 
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/monitoring.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/monitoring.mdx
@@ -5,16 +5,16 @@ description: Use the Monitor panel to track proactive health indicators and auto
 deepToC: true
 ---
 
-The **Monitoring** panel provides proactive verification of cluster health through automated canary checks. Unlike passive metrics, these checks execute active tasks to ensure the database engine is responding correctly and meeting performance baselines.
+The **Monitoring** panel on the left sidebar provides proactive verification of cluster health through automated canary checks. Unlike passive metrics, these checks execute active tasks to ensure the database engine is responding correctly and meeting performance baselines.
 
 ### Performing proactive health checks: canary checks
 
-Canary checks are recurring, automated scripts that simulate real-world operations to verify the end-to-end integrity of the system. You can configure these tests on the [User Management panel](../security/user-management).
+Canary checks are recurring, automated scripts that simulate real-world operations to verify the end-to-end integrity of the system. You can configure these tests on the [User Management panel](../system-access/user-management).
 
 Use the **Canary Checks** tab to verify that the database can successfully execute core operations.
 - **Assess overall probe health:** Review the header metrics to get an instant snapshot of system integrity. Compare the **Successful** count against the **Total Checks** count to identify if a specific subset of your monitoring is failing.
 - **Verify scheduler activity:** Check the status of the scheduler to ensure it is running. This confirms that the WarehousePG Enterprise Manager (WEM) engine is actively triggering your background probes. If the scheduler is stopped, your health data will become stale and you will lose proactive visibility.
-- **Run health checks on demand:** Trigger an immediate execution of any check in the list to verify a fix or test real-time connectivity. While you must go to the [User Management panel](../security/user-management) to create or edit a check, the **Monitoring** panel allows you to run and stop them at any time to get an instant status update.
+- **Run health checks on demand:** Trigger an immediate execution of any check in the list to verify a fix or test real-time connectivity. While you must go to the [User Management panel](../system-access/user-management) to create or edit a check, the **Monitoring** panel allows you to run and stop them at any time to get an instant status update.
 - **Benchmark execution speed:** Monitor the **Average Duration** metric to establish a baseline for expected responsiveness. A sudden spike in this metric, even if checks are still successful, serves as an early warning of resource saturation or network latency.
 - **Investigate specific check failures:** Audit the **Health Checks** table to isolate the root cause of a failure. By checking which specific probe is non-passing, you can determine if the issue is a total service outage or a localized subsystem failure.
 
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/system-metrics.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/monitoring/system-metrics.mdx
@@ -5,7 +5,7 @@ description: Use the System Metrics panel to track physical host metrics, identi
 deepToC: true
 ---
 
-The **System Metrics** panel provides a comprehensive view of the hardware and database performance telemetry across the WarehousePG (WHPG) cluster. This data is essential for identifying resource saturation, diagnosing performance degradation, and performing capacity planning.
+The **System Metrics** panel on the left sidebar provides a comprehensive view of the hardware and database performance telemetry across the WarehousePG (WHPG) cluster. This data is essential for identifying resource saturation, diagnosing performance degradation, and performing capacity planning.
 
 ### Monitoring real-time host health
 
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/performance/backups.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/performance/backups.mdx
@@ -5,7 +5,7 @@ description: Use the Backups panel to monitor data protection lifecycles, audit
 deepToC: true
 ---
 
-The **Backups** panel serves as a centralized monitoring hub for your data protection lifecycle. Use these actions to verify the integrity of your snapshots and ensure that your recovery point objectives (RPO) are being met across the WarehousePG cluster.
+The **Backups** panel on the left sidebar serves as a centralized monitoring hub for your data protection lifecycle. Use these actions to verify the integrity of your snapshots and ensure that your recovery point objectives (RPO) are being met across the WarehousePG cluster.
 
 !!! Note
     This panel requires a functional `gpbackup_manager` utility configuration to display data.
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/performance/data-analysis.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/performance/data-analysis.mdx
@@ -5,7 +5,7 @@ description: Use the Data Analysis panel to explore database structures, monitor
 deepToC: true
 ---
 
-The **Data Analysis** panel is the primary interface for auditing database structures and diagnosing storage-related performance issues. Use these actions to maintain schema health and ensure data is distributed efficiently across the cluster.
+The **Data Analysis** panel on the left sidebar is the primary interface for auditing database structures and diagnosing storage-related performance issues. Use these actions to maintain schema health and ensure data is distributed efficiently across the cluster.
 
 ### Auditing table and object inventory
 
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/performance/managing-resources.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/performance/managing-resources.mdx
@@ -4,7 +4,7 @@ navTitle: Managing system resources
 description: Use the Resource Groups panel to configure and monitor CPU, memory, and concurrency limits to optimize workload performance for resource groups and resource queues.
 ---
 
-The **Resource Management** panel allows you to govern cluster performance by controlling how system resources are distributed across different workloads. 
+The **Resource Management** panel on the left sidebar allows you to govern cluster performance by controlling how system resources are distributed across different workloads. 
 
 
 WarehousePG (WHPG) provides two primary strategies for resource management: resource groups and resource queues. They are controlled by the `gp_resource_manager` server configuration parameter. See [Managing resources](/supported-open-source/warehousepg/warehousepg/admin_guide/wlmgmt/) from the WHPG documentation for details about how WHPG provides resource management.
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/performance/query-monitor.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/performance/query-monitor.mdx
@@ -5,7 +5,7 @@ description: Use the Query Monitor panel to monitor active workloads, execute SQ
 deepToC: true
 ---
 
-The **Query Monitor** panel provides a real-time view of every session connected to the WarehousePG (WHPG) cluster. By combining live monitoring with an integrated SQL workbench and AI-assisted diagnostic tools, it allows you to maintain peak cluster performance.
+The **Query Monitor** panel on the left sidebar provides a real-time view of every session connected to the WarehousePG (WHPG) cluster. By combining live monitoring with an integrated SQL workbench and AI-assisted diagnostic tools, it allows you to maintain peak cluster performance.
 
 !!! Note 
     Access to the **Query Monitor** and its administrative functions is governed by user roles, ensuring that session management capabilities are restricted to authorized personnel.
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/performance/storage.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/performance/storage.mdx
@@ -5,7 +5,7 @@ description: Use the Storage panel to monitor disk capacity, usage distribution,
 deepToC: true
 ---
 
-The **Storage** panel provides real-time and historical visibility into disk utilization across the WarehousePG (WHPG) cluster. Use these actions to monitor current capacity, isolate hardware-specific imbalances, and forecast future storage requirements.
+The **Storage** panel on the left sidebar provides real-time and historical visibility into disk utilization across the WarehousePG (WHPG) cluster. Use these actions to monitor current capacity, isolate hardware-specific imbalances, and forecast future storage requirements.
 
 ### Monitoring cluster-wide capacity
 
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/reference.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/reference.mdx
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/reference/commands.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/reference/commands.mdx
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/reference/index.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/reference/index.mdx
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/reference/views.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/reference/views.mdx
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/system-access/access-management.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/system-access/access-management.mdx
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/system-access/index.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/system-access/index.mdx
diff --git a/advocacy_docs/supported-open-source/warehousepg/wem/system-access/user-management.mdx b/advocacy_docs/supported-open-source/warehousepg/wem/system-access/user-management.mdx
