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

# Deploy at Scale

> Deploy Engine-based monitoring and automation across many applications, servers or environments using profiles.

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

Availability
2024.1

> [card] [Profiles](#profiles)
>
> Reusable monitoring bundles

> [card] [Wizards](#wizards)
>
> Guided automated setup

> [card] [Design profiles for reuse](#design-profiles-for-reuse)
>
> Split profiles by ownership

> [card] [Validate an at-scale deployment](#validate-an-at-scale-deployment)
>
> Check before wider rollout

**Deploy Engine Monitoring and Automation at Scale**

> [!NOTE]
>
> Deploy any Engine-specfic monitoring or automation at scale using Profiles or Wizards.

GermainUX simplifies the deployment of Engine-based monitoring and automation across many applications, servers, or environments through two mechanisms:

| Mechanism | Description |
| - | - |
| **Profiles** | Profiles standardize and reuse groups of related components. |
| **Wizards** | Wizards guide administrators through common deployment scenarios. |

These mechanisms reduce repetitive configuration and help maintain consistency across large deployments.

## Profiles

A profile is a reusable set of monitoring or automation components for a single application or use case. Components within a profile typically share common configuration settings.

A profile can be used to standardize:

* Components to deploy
* Execution frequency
* Monitoring thresholds
* Application-specific settings
* Credentials or credential references
* Rules and SLAs
* Automation settings
* Target Engine or Engine group

Profiles are appropriate when the same configuration must be deployed repeatedly across multiple targets.

Example use cases include:

| Use case | Description |
| - | - |
| Applying server monitoring | Applying the same server monitoring to hundreds of hosts |
| Cross‑environment monitoring | Monitoring the same application across development, QA, and production |
| Database checks | Deploying standardized database checks |
| Log‑monitoring rules | Applying common log-monitoring rules to multiple application servers |
| Synthetic scenarios | Deploying the same synthetic scenario against many URLs |
| Standardized automation | Standardizing approved automation across multiple environments |

See Profiles for Deployment at Scale.

## Wizards

Wizards provide a guided configuration workflow for supported applications, technologies, and monitoring scenarios.

A Wizard collects the required information and automatically creates the appropriate GermainUX configuration objects. Depending on the selected Wizard, this may include:

* Application
* Monitoring profile
* Components
* Credentials
* KPIs
* Rules and SLAs
* Engine assignment
* Technology-specific settings

Wizards are appropriate when:

| When | Reason |
| - | - |
| Deploying monitoring for the first time | Deploying monitoring for the first time |
| Configuring a supported technology | Configuring a supported technology |
| Administrators need guided setup | Administrators need guided setup |
| Small set of inputs | The required configuration can be generated from a small set of inputs |
| Recommended defaults | A deployment should follow GermainUX’s recommended defaults |

See [GermainUX Wizards](https://docs.germainux.com/main/wizard.md).

## Profiles versus Wizards

| Requirement | Use |
| - | - |
| Configure a supported application through a guided process | Wizard |
| Create the initial monitoring configuration | Wizard |
| Reuse the same configuration across many targets | Profile |
| Keep related monitoring and automation components together | Profile |
| Standardize an existing configuration | Profile |
| Reduce the number of configuration decisions required during setup | Wizard |

A common approach is to use a Wizard to create the initial configuration, validate it, and then use a Profile to standardize and scale the deployment.

## Recommended deployment workflow

**1. Define the application or use case to monitor**

**2. Identify the required monitoring and automation components**

**3. Use a Wizard when one is available for the target technology**

**4. Validate the generated configuration against a test target**

**5. Group reusable components and settings into a Profile**

**6. Parameterize settings that differ between environments or targets**

**7. Assign the Profile to the appropriate Engines or targets**

**8. Deploy to a limited pilot group**

**9. Validate data collection, alerts, and automation**

**10. Expand the deployment in controlled stages**

## Design profiles for reuse

When creating a Profile:

| Guideline | Details |
| - | - |
| Focus | Keep it focused on one application or monitoring purpose. |
| Grouping | Group only components that share a lifecycle and configuration. |
| Naming | Use clear names that identify the application, environment, and purpose. |
| Environment separation | Separate environment-specific values from reusable settings. |
| Credentials | Reference centrally managed credentials instead of embedding passwords. |
| Hostnames | Avoid hard-coded hostnames when target-specific values can be supplied during deployment. |
| Documentation | Document required ports, permissions, drivers, and dependencies. |
| Ownership | Assign a configuration owner. |
| Versioning | Version and test material changes before broad deployment. |

Separate profiles may be appropriate when different teams own the components or when they require different credentials, schedules, security permissions, or release cycles.

## Validate an at-scale deployment

Before expanding beyond a pilot group, confirm that:

| Check | Detail |
| - | - |
| Correct configuration | Every intended target received the correct configuration. |
| Profile assignment | Profiles are assigned to the correct Engines. |
| Component startup | Components start without configuration errors. |
| Credentials | Credentials and permissions are valid. |
| Data mapping | Data appears under the correct application and environment. |
| Load  | Execution frequencies do not create excessive load. |
| Alerts and SLAs | Alerts and SLAs trigger as expected. |
| Automated actions | Automated actions run only on approved targets. |
| Resource utilization | CPU, memory, storage, and network utilization remain acceptable. |
| Profile updates | Removing or updating a Profile produces the expected result. |

Monitor the deployment closely as the number of targets increases. A configuration that performs well on a few targets may require additional Engine capacity at scale.

## Change management

When updating a widely deployed Profile:

**1. Back up or export the current configuration**

**2. Review the number and type of affected targets**

**3. Test the change in a non-production environment**

**4. Deploy it to a limited pilot group**

**5. Validate monitoring and automation behavior**

**6. Roll it out progressively**

**7. Confirm that all targets received the expected version**

**8. Retain a rollback procedure**

Changes to shared Profiles can affect many targets simultaneously. Treat them as controlled production changes.

## Additional Resources

> [card] [Profiles](https://docs.germainux.com/main/profiles-to-deploy-at-scale.md)
>
> And Wizard to deploy Monitoring, Analytics or Automation at scale

> [card] [Management](https://docs.germainux.com/main/management.md)
>
> More Management Features

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