Profiles: Monitoring and Automation Sets

​

GermainUX Profile Overview

A GermainUX Profile is a reusable set of monitoring and automation components for a specific application or technology. Profiles simplify deployment by grouping components that: For example, several components may require the same hostname, port, credentials, or application name. A log-monitoring component may also depend on a parser that processes the collected files. The Profile manages these shared settings and dependencies, ensuring that GermainUX deploys a component only when its required dependencies are available. Although components can be deployed individually to a GermainUX Engine, Profiles make it faster and safer to deploy monitoring and automation at scale.

​

Preconfigured Profiles

GermainUX includes preconfigured Profiles for many commonly used applications and technologies, including:

​

Apply a Profile

Before applying a Profile to a server, assign a GermainUX Engine to monitor that server.

​

Assign an Engine

You can associate an Engine with a host: Once the Engine is associated with the host, you can apply a Profile.

​

Apply the Profile to a Host

1. Go to Germain Workspace -> Left Menu -> Settings → Data Sources.
2. Open the Hosts tab.
3. Select one or more target hosts.
   
4. Click Apply Profile.
   
5. Select the Profile that matches the application or technology you want to monitor.
6. Provide the requested configuration values.
7. Click Apply.

Depending on the selected Profile, GermainUX may request:

​

Partial Profile Deployment

You may not have every required value when initially applying a Profile. For example, final credentials or log-directory paths may not yet be available. In this situation, GermainUX deploys the components that have sufficient configuration. Components missing required information remain disabled or are skipped until the missing values are provided. The successfully deployed components can begin monitoring immediately.

​

Reapply a Profile

Reapply a Profile when you need to update its settings or deploy components that were previously skipped.

1. Go to Germain Workspace -> Left Menu -> Settings → Data Sources.
2. Open the Hosts tab.
3. Select the relevant host.
4. In the details panel, locate Engine Monitoring Profiles.
5. Find the Profile you want to update.
6. Click Reapply Profile.
7. Review the stored settings and provide the updated or previously missing values.
8. Click Apply.
   

GermainUX retains the Profile’s existing settings, so you only need to update the values that have changed or were previously unavailable. After the Profile is reapplied, GermainUX deploys any components whose requirements are now satisfied.

​

Disable or Reenable a Profile

You can temporarily disable all monitoring and automation associated with a Profile—for example, when taking a server or application offline.

1. Open the host from the Data Sources page.
2. Locate the Profile under Engine Monitoring Profiles.
3. Click Disable Profile.
   

Disabling a Profile removes its components from the Engine responsible for the host. GermainUX retains the Profile configuration so it can be redeployed later. To restore the Profile and its components, click Enable Profile.

​

Automatic Profile Configuration

Manually applying Profiles is suitable for small or relatively static environments. Dynamic environments—particularly those using virtual machines, containers, or frequently changing infrastructure—can use automatic configuration rules. An Auto Config rule: For example, an Auto Config rule can automatically apply the Apache HTTP Server Profile whenever a new Engine connects for a host tagged as part of the Stage environment. To create a rule, go to the Auto Configs page in the Germain Workspace and define: Automatic configuration helps maintain consistent monitoring across rapidly changing or elastic environments.

​

Create a Custom Profile

You can create a custom Profile when: The GermainUX team can assist with designing and creating custom Profiles. Please contact us to schedule a training or configuration session.

​

Get Help

The content of this document is proprietary to GERMAIN SOFTWARE.