improve get started page

Author: mpfuster

advocacy_docs/supported-open-source/warehousepg/wem/get-started.mdx

@@ -4,51 +4,53 @@ navTitle: Getting started
 description: Learn how to access the console, understand user roles, and navigate the primary dashboard components.
 ---
 
-Once WarehousePG Enterprise Manager (WEM) is installed and the backend services are running, you can begin using it to observe system health and tune performance.
+Once WarehousePG Enterprise Manager (WEM) is installed and the backend services are running, you can begin observing system health and tuning performance.
 
+!!! Important
+    The host running WEM must remain online and the application must be active to ensure continuous data gathering. Closing the application will stop the collection of SQL and cluster-level metrics.
 
 ## Accessing the console
 
-To start using the interface:
+To begin managing your cluster:
+
 1. Navigate to your WEM server URL (e.g., `http://your-server:8080`).
-2. Enter your credentials on the login screen.
-3. Select **Sign in**.
+1. Enter your administrative credentials on the login screen.
+1. Select **Sign in**.
 
 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 post-installation
-
-Once you have installed WEM, you might need to fine-tune how WEM connects to your cluster or external services (like Prometheus and Alertmanager). There are two primary ways to manage these configurations:
+## Configuring WEM settings
 
-1. Using the WEM settings tab
+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:
 
-Administrators can modify most operational parameters directly through the browser:
+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
-    While convenient, some low-level system parameters are only accessible via the configuration file.
-
-2. Manual configuration file editing
+    Some low-level system parameters are only accessible via the configuration file.
 
-For parameters not exposed in the WEM console or for automated deployments, you can edit the configuration file directly on the host server:
+2. **Method 2: Edit the configuration file manually**
 
-    1. Stop the service: `systemctl stop wem`.
-    1. Edit the file `/etc/wem/wem.conf` on your WEM cluster and modify the desired parameter.
-    1. Restart the service: `systemctl start wem` to apply the changes.
+    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`.
 
 
 ## Navigating the interface structure
 
 The WEM interface is organized into three functional areas:
-1. **Sidebar (left)**: The primary navigation menu.
-2. **Header (top)**: Displays the current page title, system time, and global controls such as filters and refresh triggers.
-3. **Main content (center)**: The primary workspace where data tables, charts, and configuration tools are rendered.
+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
 
-WEM utilizes Role-Based Access Control (RBAC). The panels available in the console are determined by the role assigned to your user account.
+WEM utilizes Role-Based Access Control (RBAC). After the initial bootstrap, all user management and password updates are handled exclusively via the User Management panel in the UI. A user's assigned role determines which panels and actions are visible.
 
 | Role | Description | Access scope |
 | :--- | :--- | :--- |
@@ -58,39 +60,32 @@ WEM utilizes Role-Based Access Control (RBAC). The panels available in the conso
 
 Refer to the [Role permissions matrix](reference#role-permissions-matrix) for details.
 
-## Inspecting the Dashboard
+## Monitoring cluster health via the Dashboard
 
-The **Dashboard** tab is the landing page upon login, providing a real-time snapshot of cluster health and activity.
+The **Dashboard** is your landing page, providing a real-time snapshot of cluster health.
 
-### Global controls
-* **Node filter**: Scopes the dashboard metrics to a specific cluster node or all nodes for an aggregate view.
-* **Refresh**: Forces a manual update of the dashboard data points.
-* **System time**: Displays the current server-side time for synchronization reference.
+**Use the global controls**
+- **Node Filter:** Scope metrics to a specific node or view an aggregate of the entire cluster.
+- **Refresh:** Manually update all data points on the page.
 
-### Primary metrics bar
-Five high-level indicators provide an immediate status check:
-* **Uptime**: Total elapsed time since the cluster was initialized.
-* **WHPG version**: The specific version of the WarehousePG database engine.
-* **WEM version**: The current build version of the WEM application.
-* **Connections**: Total count of active database connections.
-* **Last sync**: The timestamp of the most recent data ingestion from the cluster.
+**Check primary metrics**
 
-### Status and resource summaries
-* **Segment status card**: Displays the overall operational state of the data plane. It tracks the count of healthy vs. unhealthy segments and provides a visual health bar. Select this card to access the **Cluster Overview** panel.
-* **Disk usage summary**: Provides a high-level view of storage utilization for both the coordinator and the segment nodes. Select this card to access the **Storage** panel.
+Monitor high-level indicators for an immediate status check, such as **Uptime**, **Connections**, and **Last Sync** time.
 
-### Real-time performance charts
-The dashboard includes three live charts that begin streaming data upon page load:
-* **Queries chart**: Monitors the volume of running, queued, and blocked queries.
-* **CPU chart**: Visualizes system and user CPU utilization.
-* **Memory chart**: Displays the percentage of total memory currently in use.
+**Review status and resources:**
+- View healthy vs. unhealthy segments. 
+- Monitor storage utilization for the coordinator and segments.
 
-!!! Note
-    These charts require a functional [Prometheus integration](installing/wem#configuring-wem). If you haven't configured a Prometheus service, data collection will begin when the page is loaded in the browser and the dashboard charts won't display historical data.
+**Analyze performance charts**
+
+WEM streams live data into three primary charts:
+- **Active Queries:** Track running, queued, and blocked queries.
+- **CPU Usage:** Visualize system and user utilization.
+- **Memory Usage:** Monitor total memory usage percentage.
 
-### Recent alerts
-This card displays recent WarehousePG log events. Selecting any alert will redirect you to the **Logs** panel for a deeper audit trail.
+**Audit recent alerts**
 
+Review the **Recent WHPG Log Alerts** card for WHPG log events. Open the **Logs** panel for a full audit trail.
 
 
 

advocacy_docs/supported-open-source/warehousepg/wem/monitoring/alerts.mdx

@@ -8,7 +8,7 @@ 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.
 
 !!! 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-post-installation) for details.
+    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.
 
 ### Identifying alert sources
 

advocacy_docs/supported-open-source/warehousepg/wem/performance/query-monitor.mdx

@@ -58,7 +58,7 @@ Use the **Query Editor** tab as an interactive workbench to safely explore data
 Use the integrated AI Assistant to accelerate sql authoring and simplify the debugging of complex performance issues.
 
 !!! Note
-    This is an optional feature. An administrator must configure an `ANTHROPIC_API_KEY` for the assistant to be active. See [Configuring WEM](../installing/wem#configuring-wem) and [Configuring WEM settings post-installation](../get-started#configuring-wem-settings-post-installation) for details.
+    This is an optional feature. An administrator must configure an `ANTHROPIC_API_KEY` for the assistant to be active. See [Configuring WEM](../installing/wem#configuring-wem) and [Configuring WEM settings post-installation](../get-started#configuring-wem-settings) for details.
 
 - **Generate queries from natural language:** Press `Ctrl + K` to ask the assistant to write a query for you using plain English. Because the assistant is schema-aware, it will reference your actual table and column names accurately.
 - **Optimize slow-running statements:** Paste a slow query into the assistant and ask for optimization suggestions. The assistant will analyze join efficiency, index usage, and cluster resource utilization to recommend a more efficient version of your code.