> 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/shopware/shopware6_en_us/troubleshooting-and-support/log-analysis-for-troubleshooting.md).

# Log Analysis for Troubleshooting

The Shopware 6 API Connector offers extensive logging and monitoring functions for error analysis and monitoring.

## 1. Activity Log

### Overview

The Activity Log records all important actions and events:

1. Open **Shopware** → **Activity Log**
2. You see a list of all activities

<div align="left" data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/g0yBnDwsT2m6ieFsDByB/Bildschirmfoto%202026-07-02%20um%2009.15.27.png" alt="" width="563"><figcaption></figcaption></figure></div>

### Logged events

<table><thead><tr><th width="155.4857177734375">Event</th><th width="295.5506591796875">Description</th></tr></thead><tbody><tr><td>Item upload</td><td>Item synchronized to Shopware</td></tr><tr><td>Order download</td><td>Order imported from Shopware</td></tr><tr><td>Price upload</td><td>Price updated</td></tr><tr><td>Inventory upload</td><td>Inventory synchronized</td></tr><tr><td>Picture upload</td><td>Picture uploaded</td></tr><tr><td>PDF upload</td><td>Document uploaded</td></tr><tr><td>Error</td><td>Error during an action</td></tr></tbody></table>

### Filtering and searching

You can filter the log by:

* **Date** – narrow down the period
* **Module** – only certain functional areas
* **Status** – success or error
* **Record** – a specific item, customer, etc.

## API Call Log

### Detailed API recording

For technical analysis:

1. Enable **Allow developer log** in the settings
2. Open **Shopware** → **API Calls Log**
3. You see all API calls in detail

### Logged information

| Information   | Description             |
| ------------- | ----------------------- |
| Timestamp     | When the call was made  |
| Endpoint      | API URL that was called |
| Method        | GET, POST, PUT, DELETE  |
| Request body  | Data that was sent      |
| Response code | HTTP status code        |
| Response body | Data that was received  |
| Duration      | Execution time          |

### Analyzing an API call

1. Select an entry
2. Choose **Show details**
3. Analyze the request and response

## Job Queue log

### Execution history

1. Open **Job Queue Entries**
2. Select an entry
3. Choose **Log Entries**

### Logged information

| Information   | Description                |
| ------------- | -------------------------- |
| Start time    | Start of the execution     |
| End time      | End of the execution       |
| Duration      | Total duration             |
| Status        | Success or error           |
| Error message | In case of errors: details |

## Monitoring dashboard

### Order overview

The order overview provides a quick overview:

* Number of imported orders (today/total)
* Last successful synchronization
* Open errors
* Connection status

### Status indicators

| Status    | Meaning              |
| --------- | -------------------- |
| 🟢 Green  | Everything is OK     |
| 🟡 Yellow | Warnings are present |
| 🔴 Red    | Errors have occurred |

## Error notifications

### Email notifications

Set up automatic notifications:

1. Open **Job Queue Entries**
2. Enable **Notify on error**
3. Enter the email addresses

### Notification options

| Option             | Description            |
| ------------------ | ---------------------- |
| On every error     | Immediate notification |
| Summarized daily   | Daily error report     |
| On critical errors | Important errors only  |

## Log retention

### Automatic cleanup

Logs are deleted automatically after a defined period:

* Activity Log: 30 days
* API Call Log: 7 days (when the developer log is enabled)
* Job Queue log: 30 days

### Manual cleanup

If required, you can delete logs manually:

1. Open the relevant log
2. Filter by period
3. Delete old entries

## Best practices

### Regular monitoring

* Check the activity logs daily
* React quickly to errors
* Document recurring problems

### Developer log

{% hint style="warning" %}
The developer log records detailed data and should only be enabled when required. It can affect performance and stores sensitive data.
{% endhint %}

### Log export

For support requests:

1. Filter the relevant log
2. Export the data
3. Send it to Support


---

# 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/shopware/shopware6_en_us/troubleshooting-and-support/log-analysis-for-troubleshooting.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.