> ## 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. # Profiles: Monitoring and Automation Sets > A GermainUX Profile is a reusable set of monitoring and automation components for a specific application or technology. > [card] [GermainUX Profile Overview](#germainux-profile-overview) > > Reusable bundles of components > [card] [Apply a Profile](#apply-a-profile) > > Assign an Engine first > [card] [Reapply a Profile](#reapply-a-profile) > > Update settings and skipped components > [card] [Automatic Profile Configuration](#automatic-profile-configuration) > > Profiles for dynamic environments ## 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: | Grouped characteristic | Details | | - | - | | Monitor the same application | Monitor the same application | | Share configuration values | Share configuration values | | Depend on one another | Depend on one another | | Must be deployed together | Must be deployed together | | Need to be deployed consistently across multiple servers | Need to be deployed consistently across multiple servers | 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: | Category | Profiles | | - | - | | **Web and application servers** | Apache HTTP Server, Apache Tomcat, Microsoft IIS, NGINX, PHP | | **Databases** | IBM Db2, MySQL, Oracle Database, PostgreSQL, Microsoft SQL Server | | **Infrastructure and containers** | Docker, Kubernetes | | **Messaging and coordination** | Apache Kafka, Apache ZooKeeper | | **Search and analytics** | Elasticsearch, Oracle Business Intelligence Enterprise Edition | | **Programming languages** | Go | | **Business applications** | Salesforce, Siebel CRM | ## 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: | Option | Details | | - | - | | When creating the Engine, or | When creating the Engine, or | | Later from **Germain Workspace -> Left Menu -> Germain -> State -> Engines** | Later from **Germain Workspace -> Left Menu -> Germain -> State -> Engines** | ![Profiles: Monitoring and Automation Sets: Assign an Engine](https://mintcdn.com/germain-ux/A5V4ExbdsH-e9Odt/images/main/profiles-to-deploy-at-scale/image-20240118-212155.png?fit=max\&auto=format\&n=A5V4ExbdsH-e9Odt\&q=85\&s=ae6a471a2c2e28971c78877100ca542f) 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. ![Profiles: Monitoring and Automation Sets: Apply the Profile to a Host](https://mintcdn.com/germain-ux/A5V4ExbdsH-e9Odt/images/main/profiles-to-deploy-at-scale/image-20240118-212055.png?fit=max\&auto=format\&n=A5V4ExbdsH-e9Odt\&q=85\&s=67801e883a79f0a7805990134fb39af5) 4. Click **Apply Profile**. ![Profiles: Monitoring and Automation Sets: Apply the Profile to a Host, image 2](https://mintcdn.com/germain-ux/A5V4ExbdsH-e9Odt/images/main/profiles-to-deploy-at-scale/image-20240118-212416.png?fit=max\&auto=format\&n=A5V4ExbdsH-e9Odt\&q=85\&s=d01a3674b94c72d4ef19638fdfeb653d) 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: * Application name * Hostname or port * Log or installation directories * Credentials * Connection settings * Other application-specific values ### 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**. ![Profiles: Monitoring and Automation Sets: Reapply a Profile](https://mintcdn.com/germain-ux/A5V4ExbdsH-e9Odt/images/main/profiles-to-deploy-at-scale/image-20240118-213046.png?fit=max\&auto=format\&n=A5V4ExbdsH-e9Odt\&q=85\&s=1fb26a9831b077ce4065755788075181) 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**. ![Profiles: Monitoring and Automation Sets: Disable or Reenable a Profile](https://mintcdn.com/germain-ux/A5V4ExbdsH-e9Odt/images/main/profiles-to-deploy-at-scale/image-20240118-215937.png?fit=max\&auto=format\&n=A5V4ExbdsH-e9Odt\&q=85\&s=5a9fad027de7293af15a059bd640bb06) 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. ![Profiles: Monitoring and Automation Sets: Automatic Profile Configuration](https://mintcdn.com/germain-ux/A5V4ExbdsH-e9Odt/images/main/profiles-to-deploy-at-scale/image-20240118-220901.png?fit=max\&auto=format\&n=A5V4ExbdsH-e9Odt\&q=85\&s=75052f1ddec7ead15b47a990ec69accc) An Auto Config rule: * Identifies the hosts to which it applies. * Selects the Profile that GermainUX should deploy. * Automatically applies the Profile when a matching Engine connects. 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. ![Profiles: Monitoring and Automation Sets: Automatic Profile Configuration, image 2](https://mintcdn.com/germain-ux/A5V4ExbdsH-e9Odt/images/main/profiles-to-deploy-at-scale/image-20240118-221244.png?fit=max\&auto=format\&n=A5V4ExbdsH-e9Odt\&q=85\&s=4d5bc788e455e7ab2cd35b96358fc5fe) To create a rule, go to the **Auto Configs** page in the Germain Workspace and define: * The host-selection criteria * The Profile to apply * The required Profile settings Automatic configuration helps maintain consistent monitoring across rapidly changing or elastic environments. ## Create a Custom Profile You can create a custom Profile when: * A preconfigured Profile does not exist for your application * You need to customize an existing monitoring set * You want to combine components for a proprietary application * You need a reusable automation or monitoring configuration for multiple systems ![Profiles: Monitoring and Automation Sets: Automatic Profile Configuration, image 2](https://mintcdn.com/germain-ux/A5V4ExbdsH-e9Odt/images/main/profiles-to-deploy-at-scale/image-20240118-221244.png?fit=max\&auto=format\&n=A5V4ExbdsH-e9Odt\&q=85\&s=4d5bc788e455e7ab2cd35b96358fc5fe) The GermainUX team can assist with designing and creating custom Profiles. Please [contact us](https://docs.germainux.com/main/support.md) to schedule a training or configuration session. ## 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.