GermainUX-Engine

⚙️ GermainUX Engine

GermainUX Engine executes monitoring, diagnostic, integration, and automation components close to the systems being monitored.

It retrieves its configuration from GermainUX Enterprise, executes the assigned monitoring components, and sends the resulting telemetry to GermainUX for analysis, alerts, reports, and automation.

📄 Overview

Use GermainUX Engine when monitoring or automation requires access to resources such as:

• Applications

• APIs

• Databases

• Servers

• Operating systems

• Logs

• Files

• Networks

• Messaging systems

• Cloud services

• Enterprise applications

• Third-party integrations

An Engine can run inside the same network as the monitored system, allowing GermainUX to collect telemetry without requiring direct access from GermainUX Enterprise to every protected resource.

🏗️ Architecture

A typical architecture is:

Monitored System → GermainUX Engine → GermainUX Enterprise

Each Engine host includes:

Multiple Engines can run on the same host and can be distributed across:

• Network zones

• Data centers

• Cloud regions

• Production environments

• Non-production environments

❓ When to Use GermainUX Engine

Deploy an Engine when:

• A monitored resource is not directly accessible from GermainUX Enterprise.

• Monitoring must execute within a protected network.

• Workloads need to be distributed.

• Separate production and non-production monitoring is required.

• Monitoring must operate close to a database, application, service, or infrastructure resource.

• Synthetic or automation tasks need to execute from a particular environment.

📦 Deployment Options

GermainUX Engine can be deployed on supported:

• Windows systems

• Linux systems

• Docker environments

The deployment method and requirements are documented in the Engine Deployment guide.

📋 Requirements

At a high level, an Engine host requires:

⚙️ GermainUX Engine

GermainUX Engine executes monitoring, diagnostic, integration, and automation components close to the systems being monitored.

It retrieves its configuration from GermainUX Enterprise, executes the assigned monitoring components, and sends the resulting telemetry to GermainUX for analysis, alerts, reports, and automation.

📄 Overview

Use GermainUX Engine when monitoring or automation requires access to resources such as:

An Engine can run inside the same network as the monitored system, allowing GermainUX to collect telemetry without requiring direct access from GermainUX Enterprise to every protected resource.

🏗️ Architecture

A typical architecture is:

Monitored System → GermainUX Engine → GermainUX Enterprise

Each Engine host includes:

Multiple Engines can run on the same host and can be distributed across:

❓ When to Use GermainUX Engine

Deploy an Engine when:

📦 Deployment Options

GermainUX Engine can be deployed on supported:

The deployment method and requirements are documented in the Engine Deployment guide.

📋 Requirements

At a high level, an Engine host requires:

Detailed requirements belong in the Engine Deployment guide.

🚀 Deployment Overview

A typical deployment consists of:

1. Select the Engine host.

2. Review network and software requirements.

3. Deploy Engine Manager.

4. Connect the host to GermainUX Enterprise.

5. Create or enable the required Engines.

6. Assign monitoring components.

7. Validate connectivity to monitored resources.

8. Confirm that monitoring data reaches GermainUX.

📚 Deployment and Configuration Guides

📊 Scaling

Additional Engines can be deployed when required to:

The number and placement of Engines should follow the monitoring architecture rather than a fixed deployment pattern.

🛡️ Security

Use only the connectivity and permissions required by the monitoring components assigned to each Engine.

Consider:

Avoid giving an Engine broader access than its assigned monitoring requires.

✅ Validate

After deployment, confirm:

Use Engine Troubleshooting for detailed diagnostic procedures.

📞 Support

For assistance installing, configuring, or troubleshooting GermainUX-Engine, contact GermainUX Support.