> 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/magento2_en_us/troubleshooting-and-support/monitoring-and-troubleshooting-overview.md).

# Monitoring & Troubleshooting Overview

Three log levels are available for daily monitoring:

* **Activity Log**: business flow, direction, module, success, and message
* **API Calls Log**: request URL, status, and optionally request and response data
* **Product Download Log**: progress of large product downloads

### Diagnostic Principle

1. Identify the webshop and record.
2. Read the Activity Log message.
3. For API errors, check the technical response.
4. Correct the mapping or configuration.
5. Restart only the smallest process.
6. Verify the result in BC and Magento.

### Developer Logging

The global switch enables the feature; individual scopes are activated separately.

{% hint style="danger" %}
API logs may contain customer, address, item, and document data. Enable payload logging only for a limited time.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/magento-2-api-connector/magento2_en_us/troubleshooting-and-support/monitoring-and-troubleshooting-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.