> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/magento-2-api-connector/fehlerbehebung-and-support/monitoring-and-fehlerbehebung-im-uberblick.md).

# Monitoring & Fehlerbehebung im Überblick

Für die tägliche Kontrolle stehen drei Protokollebenen zur Verfügung:

* **Activity Log**: fachlicher Ablauf, Richtung, Modul, Erfolg und Meldung
* **API Calls Log**: Request-URL, Status sowie optional Request- und Response-Daten
* **Product Download Log**: Fortschritt großer Produktdownloads

### Diagnoseprinzip

1. Shop und Datensatz identifizieren.
2. Activity-Log-Meldung lesen.
3. bei API-Fehlern technische Antwort prüfen.
4. Mapping oder Konfiguration korrigieren.
5. nur den kleinsten Prozess erneut starten.
6. Ergebnis in BC und Magento kontrollieren.

### Entwickler-Logging

Der globale Schalter aktiviert die Funktion grundsätzlich; zusätzlich werden einzelne Scopes freigeschaltet.

{% hint style="danger" %}
API-Protokolle können Kunden-, Adress-, Artikel- und Belegdaten enthalten. Aktivieren Sie Payload-Protokollierung nur zeitlich begrenzt.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.solutioo.de/magento-2-api-connector/fehlerbehebung-and-support/monitoring-and-fehlerbehebung-im-uberblick.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.