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

# Log Level Auto-setting

> GermainUX can automatically change an application’s log level when configured conditions occur.

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

Availability
2014.1 or later

> **[Automatically Adjust Application Log Levels](#automatically-adjust-application-log-levels)**
>
> Raise logging during incidents

> **[Configuration Methods](#configuration-methods)**
>
> Three ways to change levels

> **[Recommended Safeguards](#recommended-safeguards)**
>
> Limit cost and privacy risk

## Automatically Adjust Application Log Levels

GermainUX can automatically change an application’s log level when configured conditions occur.

For example, GermainUX can temporarily increase logging when an error, performance degradation, or SLA breach is detected. After the investigation period or issue resolution, it can restore the application’s normal log level.

This provides additional diagnostic detail when it is needed without requiring verbose logging to remain enabled continuously.

### Example Workflow

A typical automated workflow is:

| | Description |
| - | - |
| 1 | GermainUX detects an error, anomaly, or SLA breach. |
| 2 | An automation changes the application log level from `INFO` to `DEBUG` or `TRACE`. |
| 3 | GermainUX monitors or collects the additional diagnostic data. |
| 4 | The issue is analyzed or resolved. |
| 5 | A scheduled or event-driven action restores the original log level. |

## Configuration Methods

GermainUX supports three primary methods for changing application log levels:

| Method | Use when |
| - | - |
| **Local Program Execution** | The log level can be changed by running an executable or command available on the monitored server. |
| **Script Execution** | A Shell, PowerShell, Python, Perl, Java, or other script is required to update the application configuration or call a management interface. |
| **Rule Execution** | Custom conditions, data processing, or decision logic must determine when and how the log level changes. |

### Configure Local Program Execution

Go to:

**GermainUX Workspace > Wizards > Local Program**

![Log Level Auto-setting: Configure Local Program Execution](https://mintcdn.com/germain-ux/S6CZjLTFu68xyZFG/images/main/log-level-auto-setting/image-20260825-051210.png?fit=max\&auto=format\&n=S6CZjLTFu68xyZFG\&q=85\&s=06f9e0abadd0fb19531e70c3aa7ce9ed)

Configure the program or command that changes the application log level, then deploy it to the appropriate GermainUX Engine.

### Configure Script Execution

Go to:

**GermainUX Workspace > Wizards > Script**

![Log Level Auto-setting: Configure Script Execution](https://mintcdn.com/germain-ux/S6CZjLTFu68xyZFG/images/main/log-level-auto-setting/image-20260825-051233.png?fit=max\&auto=format\&n=S6CZjLTFu68xyZFG\&q=85\&s=5c6f7bb3cfdc8662edc2612e4918ee22)

Provide the script, required parameters, execution target, credentials, and triggering conditions.

### Configure Rule Execution

Go to:

**GermainUX Workspace > Wizards > Rule**

![Log Level Auto-setting: Configure Rule Execution](https://mintcdn.com/germain-ux/S6CZjLTFu68xyZFG/images/main/log-level-auto-setting/image-20230614-193403.png?fit=max\&auto=format\&n=S6CZjLTFu68xyZFG\&q=85\&s=50f2c63ca518601bb9671ff3ce27dcc4)

Create a rule that evaluates the required conditions and triggers the appropriate log-level action.

## Recommended Safeguards

Increasing application logging can affect performance, disk usage, data privacy, and operational cost. Before enabling automatic log-level changes:

* Limit verbose logging to the affected application, component, user, or transaction whenever possible.
* Set a maximum duration for `DEBUG` or `TRACE` logging.
* Configure an automatic action that restores the normal log level.
* Prevent repeated executions through Quiet Time or execution limits.
* Confirm that the log directory has sufficient available capacity.
* Ensure that sensitive data is not exposed through verbose logs.

> **Show all 9**
>
> * Test the action in a nonproduction environment.
> * Record who or what changed the log level and when.
> * Notify the appropriate team when logging is increased or restored.

The implementation depends on the application’s logging framework, management APIs, operating system, and deployment architecture.

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/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.