Skip to main content
ComponentsEngine
Availability2014.1 or later

Automatically Adjust Application Log Levels

Raise logging during incidents

Configuration Methods

Three ways to change levels

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:

​
Configuration Methods

GermainUX supports three primary methods for changing application log levels:

​
Configure Local Program Execution

Go to: GermainUX Workspace > Wizards > Local Program
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
Provide the script, required parameters, execution target, credentials, and triggering conditions.

​
Configure Rule Execution

Go to: GermainUX Workspace > Wizards > Rule
Create a rule that evaluates the required conditions and triggers the appropriate log-level action. 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.
  • 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

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