> ## 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.

# Deploying Linux Monitoring with GermainUX Engine: Local and Remote Configuration Guide

> Deploy Linux monitoring with the GermainUX Engine to continuously monitor the availability, health, and performance of Linux servers.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)

Availability
2014.1 or later

> **[Configure via GermainUX Wizard](#configure-via-germainux-wizard)**
>
> Pick local or remote mode

> **[Remote Linux Monitoring](#remote-linux-monitoring)**
>
> SSH-based remote collection

> **[Configure Collected Linux Metrics](#configure-collected-linux-metrics)**
>
> Choose metrics to gather

> **[Validate the Deployment](#validate-the-deployment)**
>
> Next steps after validation

## Overview

Deploy Linux monitoring with the **GermainUX Engine** to continuously monitor the availability, health, and performance of Linux servers.

> [!NOTE]
>
> GermainUX supports both **local and remote Linux monitoring**.

## Configure via GermainUX Wizard

From GermainUX Workspace, navigate to:

Left Menu
Wizards
Monitor Server

Choose whether the Linux server will be monitored locally or remotely.

## Local Linux Monitoring

Use local monitoring when GermainUX is running on the Linux server being monitored.

### 1. Select the Monitor

Under **Component Type**, search for:

**OS Monitor - Local**

Select the appropriate Linux OS Monitor.

![Deploying Linux Monitoring with GermainUX Engine: Local and Remote Configuration Guide: 1. Select the Monitor](https://mintcdn.com/germain-ux/hPK2RwO7wyn44bNw/images/main/deploying-linux-monitoring-with-germainux-engine-local-and-remote-configuration-guide/image2020-11-16_9-38-17.png?fit=max\&auto=format\&n=hPK2RwO7wyn44bNw\&q=85\&s=205494a3698a5b6694b193046ae32c48)

### 2. Select the Server

Under **Monitored Server**, select the Linux server you want to monitor.

### 3. Select the Application

Under **Monitored Application**, select the appropriate Operating System application.

Click **Next**.

### 4. Configure the Monitor

Provide a descriptive **Monitor Name**.

Select the appropriate:

* Monitoring Node
* GermainUX Engine

Configure the schedule defining how frequently Linux telemetry should be collected.

Complete the Wizard to activate monitoring.

## Remote Linux Monitoring

Use remote monitoring when a GermainUX Engine will monitor the Linux server over the network.

Remote Linux monitoring uses **SSH** to periodically connect to the monitored server and collect operating-system telemetry.

### 1. Select the Monitor

Under **Component Type**, search for:

**OS Monitor - Remote**

Select the appropriate Linux OS Monitor.

![Deploying Linux Monitoring with GermainUX Engine: Local and Remote Configuration Guide: 1. Select the Monitor, image 2](https://mintcdn.com/germain-ux/hPK2RwO7wyn44bNw/images/main/deploying-linux-monitoring-with-germainux-engine-local-and-remote-configuration-guide/image2020-11-16_9-46-45.png?fit=max\&auto=format\&n=hPK2RwO7wyn44bNw\&q=85\&s=038117c971cce2d990fa84491a401394)

### 2. Select the Server

Under **Monitored Server**, select the Linux server you want to monitor.

### 3. Select the Application

Under **Monitored Application**, select the appropriate Operating System application.

### 4. Configure SSH

Provide the SSH credentials required to connect to the monitored Linux server.

The selected GermainUX Engine must have network access to the Linux server and permission to execute the commands required for monitoring.

Click **Next**.

### 5. Configure the Monitor

Provide a descriptive **Monitor Name**.

Select the appropriate:

* Monitoring Node
* GermainUX Engine

Configure the schedule defining how frequently Linux telemetry should be collected.

Complete the Wizard to activate monitoring.

## Configure Collected Linux Metrics

GermainUX collects Linux telemetry using standard operating-system commands.

Depending on the configured monitoring scope, these can include:

```text theme={null}
/bin/cat /proc/meminfo
sar -B 1 1
vmstat 1 2
df -l
iostat -d -x
netstat -inet -na --tcp
sar -n DEV 1 3
/proc/uptime
ps -A
```

These commands provide telemetry related to areas such as:

* Memory
* CPU
* Virtual memory
* Disk space
* Disk I/O
* Network activity
* Uptime
* Processes

Individual monitoring commands and OS metrics can be configured or disabled when they are not required.

![Deploying Linux Monitoring with GermainUX Engine: Local and Remote Configuration Guide: Configure Collected Linux Metrics](https://mintcdn.com/germain-ux/hPK2RwO7wyn44bNw/images/main/deploying-linux-monitoring-with-germainux-engine-local-and-remote-configuration-guide/image2020-11-16_9-17-23.png?fit=max\&auto=format\&n=hPK2RwO7wyn44bNw\&q=85\&s=9728f5c4804c6d068ccde5f0171a1c79)

## Configure Monitoring Frequency

Configure how frequently the Linux monitor should run based on your operational requirements.

More frequent monitoring provides greater visibility into short-lived infrastructure conditions but also increases monitoring activity and data volume.

Choose a frequency appropriate for the importance and workload of the monitored server.

## Validate the Deployment

Once monitoring is enabled:

**1. Confirm the GermainUX Engine is running**

**2. Verify connectivity to the monitored Linux server**

**3. For remote monitoring, validate SSH connectivity and credentials**

**4. Confirm Linux telemetry is being received by GermainUX**

**5. Verify the expected CPU, memory, disk, network, process, uptime, and service data**

**6. Review the monitoring schedule**

**7. Configure or disable individual metrics as required**

Once validated, configure the appropriate KPIs, dashboards, alerts, SLAs, and automation for the server.

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> The Germain Team can help you set this up.

> **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.