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

# Configure a Rule for Advanced Analytics

> Rules provide an advanced way to customize GermainUX Analyticsusing custom logic.

Components
[`Engine`](/main/germain-ux-engine)

Availability
2014.1 or later

> **[Before You Begin](#before-you-begin)**
>
> Set the goal first

> **[Validate the Rule](#validate-the-rule)**
>
> Catch syntax and config errors

> **[Test the Rule](#test-the-rule)**
>
> Verify before enabling in production

> **[Security](#security)**
>
> Guardrails for powerful rules

## Creating and Configuring Rules for GermainUX Analytics

## Overview

Rules provide an advanced way to customize GermainUX **Analytics**using custom logic.

A Rule can analyze and transform data, detect conditions, generate insights or events, trigger automated actions, process action results, and determine what should happen next.

This page explains how to create, configure, test, and deploy a Rule.

## Before You Begin

Before creating a Rule, determine what you want it to accomplish.

For example:

### Analytics

* Analyze or transform monitored data
* Detect a specific condition or pattern
* Categorize or enrich data
* Correlate information
* Generate a custom metric, event, or insight

![Configure a Rule for Advanced Analytics: Analytics](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-a-rule-for-advanced-analytics/Picture2.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=d99bd0307536ea478a7c10cf7201dc45)

## Create a Rule

Go to:

**Germain Workspace > Left Menu > Settings > Analytics > Rules**

Click **+** to create a Rule.

Or start the rule creation from the **Wizard page:**

![Configure a Rule for Advanced Analytics: Create a Rule](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-a-rule-for-advanced-analytics/image-20260825-145917.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=74ce56f7eab168b0cd4645c552449a3c)

Configure the Rule properties and add the custom logic required for your use case.

![Configure a Rule for Advanced Analytics: Create a Rule, image 2](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-a-rule-for-advanced-analytics/image-20260825-150055.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=f41052f41afacb9f5c498fdeba0e1a13)

## Configure the Rule

### Name

Enter a unique and descriptive name that identifies the purpose of the Rule.

For example:

| Example Name | Code Sample |
| - | - |
| Detect Repeated Checkout Error | `Detect Repeated Checkout Error` |
| Categorize Salesforce Errors | `Categorize Salesforce Errors` |
| Analyze Slow Transactions | `Analyze Slow Transactions` |
| Trigger Remediation for Service Failure | `Trigger Remediation for Service Failure`  |

![Configure a Rule for Advanced Analytics: Name](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-a-rule-for-advanced-analytics/image-20201023-155011.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=eeef2f89af85199ed5e889113137469e)

### Rule Logic

Add the logic that GermainUX should execute.

Rules can evaluate monitored data and context to determine:

* What data should be analyzed
* Which conditions should be detected
* How data should be categorized or transformed
* Whether an event or insight should be generated
* Whether an automated action should be triggered
* How the result of an action should be processed
* What should happen next

Rules support custom expressions and logic using **MVEL**.

## Validate the Rule

After configuring or modifying the Rule, click **Validate**.

Validation helps identify syntax and configuration issues before the Rule is used.

Resolve any reported issues and validate again until the Rule is valid.

Then save the configuration.

![Configure a Rule for Advanced Analytics: Validate the Rule](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-a-rule-for-advanced-analytics/image-20260825-150204.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=9c349e6455742fd5a7b081be113b38fb)

## Assign the Rule

After the Rule has been created and validated, assign it to the GermainUX configuration or component where the custom logic should execute.

Depending on the use case, the Rule may be associated with:

* Monitoring configuration
* Analytics
* Data processing
* An automated action
* A technology-specific component

Select the Rule in the applicable configuration and save your changes.

A restart of the applicable GermainUX Engine may be required for some configuration changes to take effect.

## Test the Rule

Test custom Rules in a **non-production environment** before enabling them in production.

Verify that:

* The Rule receives the expected data
* Conditions are detected correctly
* Data is analyzed or transformed as expected
* Generated events or insights are correct
* Automated actions occur only under the intended conditions
* Action results are processed correctly
* Unexpected data does not trigger unintended behavior

For Automation Rules, also verify permissions, credentials, execution limits, and failure handling.

## Monitor the Rule

After deploying the Rule, verify its behavior using the applicable GermainUX analytics, events, logs, dashboards, or automation results.

Confirm that the Rule:

* Executes when expected.
* Produces the expected analytical result or action.
* Does not generate unnecessary events or actions.
* Handles unexpected conditions appropriately.
* Continues to behave as expected as monitored applications and data change.

## Modify a Rule

To modify an existing Rule:

**1. Go to Germain Workspace > Settings > Analytics > Rules**

**2. Select the Rule**

**3. Modify the configuration or logic**

**4. Click Validate**

**5. Resolve any validation issues**

**6. Save the Rule**

**7. Test the updated behavior before broad production use**

Changes to Rules used in production should follow your organization's testing and change-management procedures.

## Security

Rules can perform powerful analytical and automation operations.

When configuring Rules:

* Use the minimum permissions required.
* Secure credentials and sensitive information.
* Validate external inputs before using them in commands or actions.
* Limit the scope of automated actions.
* Avoid including sensitive information directly in Rule logic.
* Test potentially impactful actions in a non-production environment.
* Follow your organization's security, privacy, approval, and change-management requirements.

## Related Documentation

* [Rules — Advanced Analytics](/main/rules-advanced-automated-analytics.md)
* [Rules — Advanced Automation](/main/rules.md)
* [Analytics](/main/analytics.md)
* [Automation](/main/automation.md)
* [Automated Actions](/main/automated-actions.md)

## Get Help

> **[Contact GermainUX Support](/main/support.md)**
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.