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

# Infrastructure, Cloud and Operating Systems

> Monitor hosts, containers, cloud resources, network devices and operating systems with GermainUX, and correlate infrastructure conditions with user and business impact.

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

> [card] [What GermainUX Monitors](#what-germainux-monitors)
>
> Hosts, containers, cloud, network

> [card] [Supported Technologies](#supported-technologies)
>
> Full list of integrations

> [card] [Automation](#automation-for-infrastructure)
>
> Act on infrastructure conditions

## Overview

GermainUX monitors the infrastructure that applications and business processes depend on: physical and virtual hosts, containers, cloud resources, network devices and operating systems.

Infrastructure data is analyzed alongside user, application, code, database and integration activity. This helps teams determine whether a slow page, failed transaction or interrupted workflow is caused by an infrastructure condition, and how many users or business processes are affected.

## What GermainUX Monitors

| Area | Examples |
| - | - |
| Hosts and operating systems | Availability, CPU, memory, disk, processes, services and network |
| Containers and orchestration | Containers, images, clusters, nodes, pods, deployments, capacity and health |
| Cloud resources | Instance availability, utilization, capacity, status and operating-system metrics |
| Network | Connectivity, availability, latency, utilization, interfaces and network conditions |
| Network devices | Device status, interface traffic and errors, CPU, temperature, power and uptime over SNMP |

Available metrics depend on the technology, deployment method, accessible interfaces and installed GermainUX components.

![Docker Overview dashboard with portlets for container CPU utilization, availability, memory, disk input and output, network input and output, and container, image, network and volume events](https://mintcdn.com/germain-ux/8KX3c-GSSWR99tdN/images/main/docker-monitoring/image-20220202-205414.png?fit=max\&auto=format\&n=8KX3c-GSSWR99tdN\&q=85\&s=1a1aa73ccbda9b97d98971052e5d682d)

Docker Overview dashboard with container CPU, memory, disk, network and events - GermainUX

Network health is tracked the same way, with bandwidth and latency broken down by source and target.

![Network Overview dashboard with portlets for network bandwidth, bandwidth by system, queue length, latency, latency by source and latency by target](https://mintcdn.com/germain-ux/ARpsBmsSl-QLchOO/images/main/network-monitoring/image2020-9-11_11-30-15.png?fit=max\&auto=format\&n=ARpsBmsSl-QLchOO\&q=85\&s=cbff7f1d37da3cc6e3aa329ba1718909)

Network Overview dashboard with bandwidth and latency by source and target - GermainUX

## Supported Technologies

| Integration | Primary coverage |
| - | - |
| [AIX](https://docs.germainux.com/integrations/aix-monitoring.md) | Host availability, CPU, memory, disk, processes, services, and network |
| [Amazon EC2](https://docs.germainux.com/integrations/amazon-ec2-observability.md) | Instance availability, utilization, capacity, status, and operating-system metrics |
| [Amazon Inspector, RDS and SES](https://docs.germainux.com/integrations/aws-monitoring.md) | EC2 and container image vulnerabilities, RDS storage, and SES email delivery |
| [Docker](https://docs.germainux.com/integrations/docker-monitoring.md) | Containers, images, availability, utilization, capacity, and health |
| [HP-UX](https://docs.germainux.com/integrations/hpux-monitoring.md) | Host availability, CPU, memory, disk, processes, services, and network |
| [Kubernetes](https://docs.germainux.com/integrations/kubernetes-monitoring.md) | Clusters, nodes, pods, containers, deployments, capacity, and health |
| [Linux](https://docs.germainux.com/integrations/linux-redhat-suse-monitoring.md) | Host availability, CPU, memory, disk, processes, services, and network |
| [Network](https://docs.germainux.com/integrations/network-monitoring.md) | Connectivity, availability, latency, utilization, interfaces, and network conditions |
| [SNMP](https://docs.germainux.com/integrations/snmp-monitoring.md) | Device status, interface traffic and errors, CPU, temperature, power, and uptime over SNMP |
| [Solaris](https://docs.germainux.com/integrations/solaris-monitoring.md) | Host availability, CPU, memory, disk, processes, services, and network |

Web and application servers such as [Tomcat](https://docs.germainux.com/integrations/apache-tomcat-monitoring.md), [Nginx](https://docs.germainux.com/integrations/nginx-monitoring.md) and [IIS](https://docs.germainux.com/integrations/iis-log-parsing-monitoring.md) are listed under **Code and application runtimes** on the [Integrations overview](https://docs.germainux.com/integrations/monitoring.md#supported-integrations).

## Analyze Infrastructure Impact

Infrastructure metrics become more useful when connected to the users and workflows they affect. With GermainUX you can:

* Correlate host, container and network conditions with slow user interactions, errors and failed transactions. See [Correlation and Tracing](https://docs.germainux.com/analytics/correlation-and-tracing.md).
* Separate infrastructure events with no observed user impact from those affecting users or business processes. See [Impact at Scale for Any Issue](https://docs.germainux.com/analytics/business-impact-at-scale-for-any-issue.md).
* Detect abnormal trends and spikes in capacity or utilization. See [Outlier and Anomaly Detection](https://docs.germainux.com/analytics/outlier-detection.md).
* Define thresholds and alerts with [SLAs](https://docs.germainux.com/analytics/slas.md).
* Investigate a condition from the KPI to the affected population in the [Analysis Dashboard](https://docs.germainux.com/dashboards/analytics-dashboard/4-analysis-dashboard.md).
* Monitor overall health in real time on the [Operational Dashboard](https://docs.germainux.com/dashboards/operational-dashboard.md).

## Automation for Infrastructure

Infrastructure components can also be targets for GermainUX actions, run manually, on a schedule or when a configured condition is met.

| Action | Use |
| - | - |
| [SSH](https://docs.germainux.com/automation/ssh-execution.md) | Execute authorized commands on remote Linux and Unix hosts |
| [WMI](https://docs.germainux.com/automation/wmi-execution.md) | Query or manage authorized Windows systems |
| [Scripts](https://docs.germainux.com/automation/script.md) | Run configured diagnostic, maintenance or recovery scripts |
| [Local programs](https://docs.germainux.com/automation/local-program-execution.md) | Run authorized programs and commands, such as restarting a service |
| [File purge](https://docs.germainux.com/automation/automatic-delete-purge-of-files.md) and [archiving](https://docs.germainux.com/automation/file-archiving.md) | Manage disk usage by removing or archiving files |
| [Alerts](https://docs.germainux.com/automation/notifications/alert-email-and-sms.md) | Notify the responsible team when a condition is detected |

See [Automation](https://docs.germainux.com/automation.md) for all available actions.

## Deployment

Infrastructure monitoring is typically collected by the [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md), locally or remotely, and by the [GermainUX Agent](https://docs.germainux.com/deploy/germainux-agent.md) on supported hosts. See each technology page above for its specific deployment and configuration steps.

> [!WARNING]
>
> Use least-privilege credentials for monitoring and actions, and follow the organization's security, approval and change-management policies. See [Compliance, Privacy and Security](https://docs.germainux.com/management/compliance-privacy-and-security.md).

## Related Pages

> [card] [Integrations Overview](https://docs.germainux.com/integrations/monitoring.md)
>
> All supported integrations

> [card] [Middleware and Integrations](https://docs.germainux.com/integrations/middleware-and-integrations-monitoring.md)
>
> Queues, messaging and services

> [card] [Data Sources](https://docs.germainux.com/management/data-source.md)
>
> Hosts, databases, files and URIs

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/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.