> ## Documentation Index > Fetch the complete documentation index at: https://docs.germainux.com/llms.txt > Use this file to discover all available pages before exploring further. # Germain Health > Monitor and manage the health of Germain Enterprise and its runtime services. Service `Management` Availability 2016.1 or later > [card] [GermainUX Workspace](#germainux-workspace) > > State dashboard overview > [card] [Nodes](#nodes) > > Inspect and manage nodes > [card] [JavaScript Deployments](#javascript-deployments) > > Monitor JS deployment status > [card] [Remote Troubleshooting](#remote-troubleshooting) > > Investigate entities remotely ## GermainUX Health and Runtime Management GermainUX provides three ways to monitor and manage the health of Germain Enterprise and its runtime services: | Option | Description | | - | - | | **GermainUX Workspace** | Centrally monitor, configure, start, stop, restart, update, and troubleshoot GermainUX services and components. | | **GermainUX Sentinel** | Independently monitors GermainUX and automatically restarts failed services or components. | | **Local machine** | Inspect and manage a GermainUX service directly from the server or workstation on which it runs. | ### GermainUX Workspace The **State** dashboard provides administrators with a centralized view of GermainUX runtime health. Go to: **GermainUX Workspace > Germain > State** ![Germain Health: GermainUX Workspace](https://mintcdn.com/germain-ux/8KX3c-GSSWR99tdN/images/main/germain-health/image-20260825-212126.png?fit=max\&auto=format\&n=8KX3c-GSSWR99tdN\&q=85\&s=07d68d1b5bfad7f3cdbaf723c8603e1d) > [!NOTE] > > From this dashboard, authorized administrators can: * Review service and component status * Start, stop, or restart supported services * Monitor queues * Manage Nodes and Engines * Deploy or update components * Review agents, JavaScript deployments, and browser extensions * Investigate configuration or runtime failures ### Enterprise Services Verify that all required Germain Enterprise services are running. | Service | Responsibility | | - | - | | **Ingestion Service** | Receives and processes incoming monitoring data. | | **Session Tracking Service** | Tracks and correlates monitored user sessions. | | **Analytics Service** | Executes analytics and insight-processing workloads. | | **Aggregation Service** | Produces aggregated data used by dashboards and reports. | | **Action Service** | Executes alerts, reports, scripts, and other automated actions. | | **Storage Service** | Stores processed monitoring data in the configured datastore. | | **REST Service** | Provides supported REST interfaces used by GermainUX components and integrations. | The services required in a specific environment depend on its architecture and enabled capabilities. ### Queues Use the **Queues** tab to review GermainUX processing queues. Monitor: * Current queue depth * Whether the queue is growing or shrinking * Processing rate * Data-ingestion rate * Age of the oldest queued item * Failed or repeatedly retried items Queues do not always need to remain at zero, particularly in busy environments. However, a continuously growing backlog may delay analytics, alerts, automated actions, and dashboard updates. Evaluate whether each queue is being processed quickly enough to meet your organization’s real-time requirements. ![Germain Health: Queues](https://mintcdn.com/germain-ux/8KX3c-GSSWR99tdN/images/main/germain-health/image-20260825-212159.png?fit=max\&auto=format\&n=8KX3c-GSSWR99tdN\&q=85\&s=c6cdbec92ae376c1686568c01bc493c7) ### Nodes Use the **Nodes** tab to review and manage GermainUX Nodes. From this tab, administrators can inspect: * Node availability * Runtime status * Associated Engine Managers * Deployed services and components * Configuration or communication issues ### Engines Use the **Engines** tab to review and manage GermainUX Engine instances. Available operations may include: * Review Engine status * Start or restart an Engine * Inspect deployed components * Review configuration * Troubleshoot failed monitoring or automation * Manage supported Engine updates #### Engine Auto-Configuration Engine auto-configuration helps standardize Engine deployment and configuration across applicable Nodes and environments. Review the generated configuration before applying it to production systems. ### Components Use the **Components** tab to manage deployed GermainUX component instances. Depending on the component and user permissions, administrators can: * Review operating status * Inspect configuration * Deploy a component * Update a component * Enable or disable execution * Configure a schedule * Restart the component * Investigate failures #### Component Types A component represents a monitoring, analytics, or automation workload executed by a GermainUX Engine. The available component types depend on the technologies and capabilities enabled in the environment. #### Component Scheduling Components that support scheduled execution can run: * Every minute * Hourly * Daily * Weekly * At specified times * According to an advanced CRON expression Enable **Run on Schedule** in the applicable component configuration and define the required schedule. See [Scheduling an Action](https://docs.germainux.com/main/component-scheduling.md) for scheduling options and CRON-expression examples. ### JavaScript Deployments Use the **JS Scripts** tab to manage JavaScript monitoring deployments, including: * [GermainUX RUM JS](https://docs.germainux.com/main/germain-ux-rum-js.md) * [GermainUX JavaScript Profiler](https://docs.germainux.com/main/germain-ux-js-profiler.md) From this tab, administrators can review deployment and operating status for the JavaScript monitoring associated with their applications. ### Agents Use the **Agents** tab to review and manage GermainUX monitoring agents. Administrators can use this view to: * Confirm that agents are connected * Review their versions and status * Identify inactive or unhealthy agents * Troubleshoot communication issues * Perform supported management operations ### Browser Extensions Use the **Browser Extensions** tab to review and manage GermainUX browser-extension deployments. GermainUX browser extensions can be distributed through supported public browser stores or hosted within an organization’s private store or cloud environment. ### Remote Troubleshooting The State dashboard helps administrators remotely investigate GermainUX entities such as: * Enterprise services * Nodes * Engines * Components * Agents * Browser extensions * JavaScript monitoring deployments When troubleshooting, review the entity’s status, configuration, logs, queue activity, connectivity, and recent execution history. ## Local Machine Management A GermainUX runtime can also be inspected directly from the machine on which it operates. Examples include: * An Engine running on an application server * An agent running within an application environment * A browser extension installed on a user workstation * A Germain Enterprise service running on its host Local access can help diagnose operating-system, network, permission, process, log, or startup issues that are not visible from the Workspace. ## GermainUX Sentinel **GermainUX Sentinel** is an independent self-monitoring capability that helps maintain GermainUX availability. Sentinel can: * Monitor the health of GermainUX services and components * Detect stopped or failed processes * Automatically restart supported services or components * Reduce the need for manual recovery * Help maintain continuous platform operation See [GermainUX Sentinel](https://docs.germainux.com/main/sentinel.md) for more information. ## Get Help > [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md) > > The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes. > [card] Can't find what you need? > > Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing. The content of this document is proprietary to GERMAIN SOFTWARE. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.