Skip to main content
With the LogManager, logs can be captured, bundled, and evaluated in a targeted way. Log groups can be defined to specify which messages from which areas are to be collected.

Calling the service

You can call it via the following URL:

General

The service is only visible if the required permission is available. If the service is not visible, please contact your shop administrator. In the LogManager, logs are always recorded via log groups. In a log group, you specify which log entries are to be collected. You can narrow entries down or combine messages from several areas into one common group. For each log group, a descriptive label and a description must be entered. This makes it easier to understand later which logs are recorded in the respective group. In addition, an email notification can optionally be set up for each log group.

Explanation of the filters

Log category

Defines from which business or technical area log entries are included in the log group. For better understandability, the category is displayed with a descriptive label, supplemented by the technical category name in parentheses.

Administration, configuration & system

App API & input assistants

Imports, exports, and data feeds

Images, videos, and media processing

Email, newsletter, and notifications

Payments and PayPal

Plugins

Programs and background processes

Automation and messaging

REST API

SEO, content, and other services

Log level

Defines which type of log entries are included in the log group. The log level describes the meaning or severity of an entry – from purely informational messages to critical errors.

Program

The Program field defines which technical service or processing area log entries are included in the log group from. Since the technical names are not always self-explanatory, it is recommended to use a descriptive label with the additional technical name for display.

Keyword

Content search in the log files themselves Using the keyword, log entries can additionally be filtered based on their content. This allows the log group to be narrowed down to specific error messages, technical terms, or error codes. For example, a log group for critical errors can additionally be restricted to specific error messages or known error codes.

Subshops

Using this filter, you can specify which subshops are included in the log group. This way, logging in multi-shop environments can be targeted at individual shop areas. This is especially useful when a platform contains multiple subshops and logs are to be evaluated only for a specific shop.

Email notifications

For log groups, email notifications can optionally be set up. You can specify that for newly captured log entries, a notification is automatically sent by email. The sending does not take place immediately for each individual entry, but based on a configurable time interval. In addition, you can specify the date and time from which the first notification should be sent. From that point on, the set interval applies for further notifications. As recipients, one or more email addresses can be entered. The notification emails contain links to the service and to the associated log group, so that the relevant entries can be opened directly. By default, no email notifications are sent. A notification is only sent if this function has been explicitly configured for the respective log group.