Architecture
Components and distribution
Deployment Options
Infrastructure and release factors
Deployment Overview
Stages from install to live
Deploy Monitoring Or Automation Components
Deploy components by use case
Overview
GermainUX Enterprise is the central GermainUX platform used to:
Additional GermainUX components are deployed according to the applications, technologies, infrastructure, and users being monitored.
When to Use an On-Premise Deployment
Choose this deployment model when your organization needs direct control over:- Infrastructure
- Data location and residency
- Network architecture
- Platform security
- Authentication
- Backup and disaster recovery
Show all 10
Show all 10
- High availability
- Upgrade scheduling
- Data retention
- Integration with internal systems
Architecture
A typical architecture includes:
Components can be distributed across multiple:
- Servers
- Network zones
- Data centers
- Cloud regions
- Production and non-production environments
Deployment Options
Depending on your infrastructure standards and GermainUX release, GermainUX Enterprise can be deployed using supported:- Server-based installations
- Docker
- Kubernetes
- Red Hat OpenShift
- Cloud-hosted virtual machines within your account
- Number of monitored users
- Data volume
- Session Replay volume
- Code-profiling volume
- Retention
- Availability requirements
- Security requirements
- Number of environments
Before You Begin
Before starting an on-premise deployment:1
Define the applications and technologies to monitor
2
Estimate monitoring volume and retention
3
Select the deployment architecture
4
Review infrastructure requirements
5
Identify the systems that will host GermainUX Enterprise and its supporting components
6
Obtain the required GermainUX packages and license
7
Prepare network, DNS, certificates, and security controls
8
Install GermainUX Enterprise
9
Deploy the required monitoring components
10
Validate end-to-end monitoring
Requirements
Review hardware, software, network, storage, and infrastructure requirements before provisioning GermainUX Enterprise. Review GermainUX Enterprise Requirements Detailed requirements are maintained on the dedicated Requirements page and should not be duplicated here.Package and License
Obtain the GermainUX packages and license appropriate for your deployment before installation. Obtain GermainUX Packages and License The Package and License guide contains the detailed package structure, license requirements, and preparation steps.Deployment Overview
A typical deployment follows these stages:1. Prepare the Infrastructure
Provision the compute, storage, operating system or container platform, networking, DNS, and certificates required by the selected architecture.2. Prepare the Datastore
Deploy the supported datastore architecture required for GermainUX Enterprise.3. Install GermainUX Enterprise
Install the central GermainUX services.4. Apply the GermainUX License
Configure the license issued for the environment.5. Configure Enterprise
Configure the required environment-specific services, authentication, integrations, and operational settings.6. Validate GermainUX Enterprise
Confirm that GermainUX Enterprise is operational and administrators can access Germain Workspace.7. Deploy Monitoring Components
Deploy only the GermainUX components required for your monitoring and automation use cases.8. Validate End-to-End Monitoring
Confirm that telemetry is reaching GermainUX and appears correctly in analysis, dashboards, alerts, reports, and Session Replay where applicable. Detailed commands and installation procedures belong in the Installation child page.Deployment Guides
Deploy Monitoring Or Automation Components
Once GermainUX Enterprise is operational, deploy only the components required for your use cases:Management Responsibilities
With an on-premise deployment, your organization typically manages:- Infrastructure
- Operating systems or container platforms
- Network
- DNS
- Certificates
- Firewalls
- Backup and disaster recovery
- GermainUX Enterprise operation
- GermainUX software
- Licenses
- Product updates
- Documentation
- Product-specific support
- Deployment assistance
Security and Data Privacy
Before production use, define:- Applications and users that may be monitored
- Data that may be collected
- Data that must be excluded
- Masking and anonymization
- Session Replay permissions
- User and administrator access
Show all 10
Show all 10
- Retention
- Backup protection
- Certificate and key management
- Audit and change-management requirements
Validate
At the parent-page level, successful deployment means:- GermainUX Enterprise is available.
- The datastore is connected.
- Administrators can authenticate.
- Required services are healthy.
- Monitoring components can connect.
- Telemetry is received.
Show all 10
Show all 10
- Dashboards and analysis contain expected data.
- Alerts operate correctly.
- Session Replay works where enabled.
- Privacy controls work as expected.
Get Help
Contact GermainUX Support
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.