> ## 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 File Analysis

> GermainUX analyzes log files from any technology, detects errors and abnormal behavior, and automatically triggers notifications and actions.

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

Availability
2021.1 or later

> [card] [Any Technology](#any-technology)
>
> Logs from any source

> [card] [What GermainUX Detects](#what-germainux-detects)
>
> Errors, outliers and more

> [card] [Automated Actions](#automated-actions)
>
> Respond to log insights

> [card] [Get Started](#get-started)
>
> Set up log analysis

## Overview

GermainUX analyzes log files generated by **any technology**. The [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md) detects new or changed log files, parses them into structured events, metrics, or transactions, and analyzes them in real time or on a schedule.

Within Automation, log analysis turns log content into conditions that can trigger notifications and approved actions automatically, so teams do not need to search production logs manually.

Collect
Parse
Analyze
Act
Validate

## Any Technology

GermainUX can analyze logs generated by:

* Applications and custom software.
* Web and application servers.
* Databases.
* Operating systems.
* Containers.
* Integration platforms.
* APIs and services.
* Authentication systems.
* CRM, ERP, and eCommerce applications.

Supported formats include plain text, application and system logs, JSON, CSV and other delimited data, XML, fixed-width records, and compressed archives such as ZIP.

Preconfigured parsers are available for supported applications, infrastructure technologies, and common formats. For any other log format, a custom parser can be built with [GermainUX Rules](https://docs.germainux.com/automation/rules.md) to:

* Identify record boundaries, including multiline records.
* Extract fields such as timestamp, severity, host, user, session, transaction ID, error code, message, and duration.
* Create events, metrics, or transactions.
* Categorize errors and exclude irrelevant records.
* Add application or environment context.

## What GermainUX Detects

| Detection | Examples |
| - | - |
| Errors | Exceptions, warnings, error codes, integration and authentication failures |
| New and recurring issues | Newly observed messages, recurring errors grouped by [Categorization](https://docs.germainux.com/analytics/data-categorization.md) |
| Performance | Degradation, abnormal processing duration, throughput changes |
| Availability | Crashes, restarts, startup, shutdown, and connection events |
| Outliers | Sudden error spikes, missing or delayed files, unexpected record volume |
| Business failures | Application-specific failures in business processes |

Log events can be correlated with user sessions, Session Replay, network requests, application transactions, database activity, infrastructure metrics, and business processes. See [Correlation and Tracing](https://docs.germainux.com/analytics/correlation-and-tracing.md).

Custom KPIs can be created from any parsed value. See [KPIs Management](https://docs.germainux.com/management/manage-kpis.md).

## Automated Actions

When log analysis detects a qualifying condition, GermainUX can trigger approved actions such as:

* Alerts by email, Slack, Microsoft Teams, or other [notifications](https://docs.germainux.com/automation/notifications.md).
* [Watches](https://docs.germainux.com/automation/notifications/watch.md) and [automatic reports](https://docs.germainux.com/automation/notifications/reporting-automatic.md).
* Incident creation in [ServiceNow](https://docs.germainux.com/automation/servicenow.md) or [Moogsoft](https://docs.germainux.com/automation/moogsoft.md).
* [Script](https://docs.germainux.com/automation/script.md), [local program](https://docs.germainux.com/automation/local-program-execution.md), [SQL](https://docs.germainux.com/automation/sql-execution.md), or [SSH](https://docs.germainux.com/automation/ssh-execution.md) execution.
* [File download](https://docs.germainux.com/automation/file-download.md), [file archiving](https://docs.germainux.com/automation/file-archiving.md), or [file purging](https://docs.germainux.com/automation/automatic-delete-purge-of-files.md).
* A temporary increase in log detail with [Log Level Auto-Setting](https://docs.germainux.com/automation/log-level-auto-setting.md).

## Get Started

**1. Deploy a GermainUX Engine**

Install the [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md) where it can securely access the log files.

**2. Create a Directory Monitor**

Go to **Settings > Wizards > Directory Monitor Deployment**, then select the Engine, server, directory path, file patterns, and collection interval.

**3. Select or build a parser**

Use a preconfigured parser where available, or create a custom parser with [GermainUX Rules](https://docs.germainux.com/automation/rules.md).

**4. Configure KPIs, alerts, and actions**

Define the conditions of interest and the automated response.

**5. Validate**

Generate a controlled test condition and confirm the expected alert or action.

> [!NOTE]
>
> Logs can contain sensitive information. Collect only what is needed, [mask or exclude sensitive fields](https://docs.germainux.com/management/compliance-privacy-and-security/data-privacy.md), and restrict access to original files.

For full deployment, parser, remote collection, file rotation, and security details, see [Files / Logs Observability](https://docs.germainux.com/integrations/file-log-monitoring.md).

## Get Help

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