# Analyse an error log | IT-INTERDEV

> The AI finds the cause. Passwords and customer names stay secret. This example is made up.

Language: en · Source: https://it-interdev.de/en/use-cases/analyze-an-error-log.html · Alternate (de): https://it-interdev.de/anwendungen/fehlerprotokoll-analysieren.html · Updated: 2026-10-05

**Zone**: Yellow · **Software development and IT**

## The situation

A program crashes. The log has many lines. In between are passwords, server names and customer data.

## How it works

1. You paste the log.
2. **The Schleuse replaces secrets.** Names, addresses, identifiers and credentials are replaced with stand-in words. This happens on your side, not in the cloud. Amounts and dates stay as they are.
3. **The AI answers, the Schleuse translates back.** The answer contains the stand-in words. On your side they turn back into the real names.

## Example

**Your question to the AI:** What is the cause of this error? What should I check first?

**What is in your text:**

> ERROR connection to **db01.mueller-landtechnik.intern** failed.
> User **abrechnung**, password **Wint3r2026!**.
> Customer **Müller Landtechnik GmbH**.

**What the cloud AI sees:**

> ERROR connection to **DatabaseServer_A** failed.
> User **User_A**, password **Password_A**.
> Customer **Company Alpha**.

*This example is made up.*

## What you get

You get possible causes and steps to check.

## Good to know

The Schleuse has been tested on texts and documents. A separate test series for logs is still to come.

## Zone of this use case: Yellow

Only through the Schleuse. And only to targets you have approved.

## Status of the Schleuse

Version 0.1 Alpha. So far tested only with made-up examples. Not reviewed by third parties. No legal advice.