Data log
Events in your system are logged in the menu Data » Log. This allows you to check the data log for errors without relying on our support.
Events with the severities Error, Critical, Alert and Emergency are logged automatically. You can activate logging of other events for a limited time if and when needed.
1. What is the data log?
The data log documents events that occur in your system.
-
Each log entry is equivalent to one event in your system.
-
Each log entry is available for four weeks after the event. After that time, the log entry is deleted automatically.
-
Events can have different degrees of severity. In PlentyONE. these different severities are called log levels.
-
Events with the log levels Error, Critical, Alert and Emergency are logged automatically.
-
The log levels Debug, Info, Notice and Warning are not logged by default. Instead, you need to activate them to document events with this severity. (How?)
-
Each log entry contains the following information about the event:
Timestamp |
The date and time of the event |
Level |
The severity of the event |
Integration |
The area of the system in which the event too place. Examples:
|
Identifier |
The sub area of the system in which the event too place. Examples:
|
Reference type |
The type of record: For example, is it an address ID, a catalogue name or the ID of an Etsy listing? |
Reference value |
The value of the record to which the event relates. For example, this could be the ID of an item, of a variation or of a category. |
Message |
A description of the event |
Log details |
Click on the log entry to show more details. More information about the event is displayed. In this window, you can also jump to the previous or next log entry. In addition, you can show or hide the information. |
2. What do the log levels mean?
Log level | Description | Activated by default |
---|---|---|
Debug |
Detailed status messages |
No |
Info |
General information about the system |
No |
Notice |
An error message that should be dealt with, but is not urgent. |
No |
Warning |
Something is not working as intended. However, it might not be an error. |
No |
Error |
Standard system error; when errors occur, the system usually keeps running. |
Yes |
Critical |
These errors can cause a system crash. |
Yes |
Alert |
You need to react immediately. |
Yes |
Emergency |
Absolute emergency. The system is unusable. |
Yes |
3. Finding log entries
When you open the menu Data » Log, a list of all logged events for the default client is shown. This list is sorted by date and time. As such, the latest event is at the top of the list.
You can filter the log entries to reduce the list of events and make it more manageable.
Filtering the list of log entries:
-
Go to Data » Log.
→ All logged events of the default client are shown. -
At the top left of the toolbar, click on (tune).
→ The available filters are shown. -
Select the filters you want to apply. Note the explanations in Table 2.
Is a filter missing from the drop-down lists?
The drop-down lists only contain filters for events for which log entries exist. So if for example you cannot select a filter for OTTO Market from the list, that means that no events were logged for this market in the last four weeks. -
Click on () Search.
→ The filtered log entries are shown.
Could not find the log entry you were looking for?
Not all events are logged by default. So you might have to activate the logging for the event you are trying to find.
Filter | Explanation |
---|---|
Client |
By default, the list is filtered to only show log entries for the default client. To show events for another client (store), select that client (store) from the drop-down list. |
Integration |
The area of the system in which the event too place. Examples:
|
Identifier |
The sub area of the system in which the event too place. Examples:
|
Level |
The severity of the event. |
Reference type |
The type of record: For example, is it an address ID, a catalogue name or the ID of an Etsy listing? |
Reference value |
The value of the record to which the event relates. For example, this could be the ID of an item, of a variation or of a category. |
Date from |
Click on the calendar icon to select a date. |
Time from |
Enter a time in the format HH:MM:SS. |
Date to |
Click on the calendar icon to select a date. |
Time to |
Enter a time in the format HH:MM:SS. |
4. Activating optional logging
Events with the log levels Error, Critical, Alert and Emergency are logged automatically. However, to log events with the log levels Debug, Info, Notice or Warning, you need to activate logging first.
-
Logging ends automatically once the duration you set is up.
-
You are unsure about what to log and confused about integrations, reference types and identifiers? For many markets, you can find info on what to filter for on the manual page for that market. Or head to the forum to ask which system areas you need to log to find out what’s going on.
Activating optional logging:
-
Go to Data » Log.
→ All events logged for the default client are shown. -
In the top left of the toolbar, click on Configure logs ().
→ The window Log configuration opens.
→ On the left side, the system areas and any installed plugins are listed. -
Select the area in which you want to configure logs.
→ On the right side, the settings for the area you selected are shown. -
Activate the option Active.
-
In the drop-down list Duration, select how long you want to log events for this area.
-
In the drop-down list Log level, select the events that you want to log.
What do the log levels mean? -
Save () the settings.
→ The logging of the events starts.
→ Logging ends automatically once the duration you set is up.
Important: The first log entry only becomes available once the event that you want to log next occurs.