Logs
Search platform and application logs by date, time, and key; examine request, response, and error details with masked payloads.
The Logs screen allows you to search and examine records left by applications and channel integrations individually. Answers to questions like "What happened to this order?" or "What response did the integration give to this request?" are mostly found here. There are two separate log sources on the screen: Platform logs (application and integration request/response records) and Application logs (operation records written by applications in your workspace). The two sources do not contain the same data; if you cannot find what you are looking for in one, check the other. This screen is mostly used by support and operations teams investigating integration issues.
Accessing the screen
- Navigate via the menu: ComHub – Marketplace Integration › Visibility › Logs. The screen opens in the Platform logs view.
- You can also reach the Platform logs view by clicking the Logs box in the Visibility card on the ComHub Overview page.
- In the OMS Queue screen, the Show logs link on a record opens the Application logs view filtered by that record's key in a new tab.
If you do not see it in the menu, your account does not have permission for this screen.
Screen sections
- Title: shows Platform logs or Application logs depending on the selected view.
- View tabs: Platform logs and Application logs.
- Filter area: date, time, and view-specific fields; below are Clear, Detailed filters, and Filter buttons.
- List: with Per page selection above, text showing Filter result: [number] records, refresh button, and Columns menu.
- Note: below the list, a brief explanation reminding the default date range and the widest range.
Changing the view
Clicking a tab changes the view immediately. When the view changes, all filters, date range, and page reset because the two sources interpret dates and default ranges differently. Re-enter your filters in the new view.
Filtering and searching
Filters are not applied until you press the Filter button (or Enter in a field); if there are unapplied changes, the Filter button is highlighted. Pressing Filter without changing filters refreshes the list with current data. Clear resets all filters and immediately refreshes the list. You can open and close additional filter fields from the Detailed filters menu; your choice is remembered in your browser. Closing a field clears its value.
Date and time (common to both views)
| Field | Purpose | Tip |
|---|---|---|
| Date range | Filters by the day the record was created. The end day is inclusive. | If left empty, the last 24 hours are queried in Platform logs, and the last 10 days in Application logs. The maximum range is 31 days. |
| Start time | Excludes records before this time on the start day. | Enter in HH:mm format, e.g., 09:30. If you enter time without a date, today is used as the day. |
| End time | Excludes records after this time on the end day. The entered minute is included. | Enter in HH:mm format. |
If you enter time in an incomplete or unreadable format like 9:5, a warning appears above the filter field: Time could not be read: "[value]". Enter in HH:mm format (e.g., 09:30). and the list is empty. Correct the time and press Filter again.
Tip: In Platform logs, the date and time are interpreted according to the time zone you use on the screen. In Application logs, times are the server time where the record was written and are not converted; enter the time considering this difference.
Platform logs filters
| Field | Purpose | Tip |
|---|---|---|
| Session key | Retrieves records for specific session keys. Visible by default. | You can search for multiple values: the Enter multiple values button to the right opens a window; paste one value per line and press Apply. Pasting multi-line text directly into the field has the same effect. |
| Request id | Retrieves records for a single request. | Open from the Detailed filters menu. |
| Parameter text | Searches by the record's parameter text. | Open from the Detailed filters menu. |
Application logs filters
| Field | Purpose | Tip |
|---|---|---|
| Key | Filters by the record's key. The placeholder text gives examples like Order no, customer code… | Always visible. |
| Log name | Retrieves records with a specific log name. | Visible by default. |
| Type | All, Info, or Error. | Visible by default. Select Error to see only errors. |
| Request/response | All or With body only. | Visible by default. With body only shows records with saved request/response content. |
List
Platform logs columns
| Column | Meaning |
|---|---|
| Endpoint | The path of the request; below in faint text, the caller information. This column cannot be hidden. |
| App | The application that wrote the record. |
| User | The user who made the request. Hidden by default due to personal data. |
| Type | Record type badge. Error and above are red, warning yellow, info blue, others gray. |
| Duration | Request duration in milliseconds (e.g., 120 ms). |
| Session key | The session key associated with the record. |
| Log name | The log name of the record. Hidden by default. |
| Request id | The request ID. Hidden by default. |
| Time | The date and time the record was created, including seconds. |
Application logs columns
| Column | Meaning |
|---|---|
| Log name | The log name of the record; below in faint text, the caller information. This column cannot be hidden. |
| App | The application that wrote the record. |
| Key | The record's key (order no, customer code, etc.). |
| Type | Record type badge: Error red, Warning yellow, Info blue, others gray. |
| Payload | Shows Exists badge if request/response content is present; otherwise —. |
| Record no | The record's number. |
| Time | The date and time the record was created, including seconds; server time, unconverted. |
In both views:
- Page size can be 25, 50, or 100; default is 25.
- You can hide or show columns from the Columns menu; your choice is saved in your browser.
- Clicking column headers does not sort.
- Clicking a row or selecting Open detail from the three-dot menu opens the record's detail page.
Log detail page
The detail page shows all fields and content of the record. The Back to logs button returns to the previous page in the browser; if you came from the list, it opens with the filters you left. The title shows the record's path or log name; below are the application and caller author; top right is the record's type badge (red if the platform log record carries an error, gray otherwise). If the record has an error, a warning with the error message (or This record carries an error.) appears at the top of the Promotion capture tab.
Platform log tabs
- Promotion capture: fields are shown in two cards. First card: Record no, Endpoint, Caller, App, Type, Log name, Query string, Description. Second card: Time, Request time, Response time, Duration, Request id, Session key, User, IP address, Machine, Server, Workspace. Empty fields show as
—. Share Record no when describing the record in support requests. - Request: the request body. Always visible; if no body is saved, a blank state message appears.
- Response: the response body (same behavior).
- Log content: visible if the record has content separate from request and response.
- Bug: visible if the record carries an error; shows Error message, Error source, and detailed error dump if available.
Application log tabs
- Promotion capture: first card shows Record no, Key, Time (server time, unconverted), App, Caller, Log name; second card shows Type, Level (numeric), Machine, Correlation id, Description.
- Payload: the record's content.
- Bug: visible if the record carries an error; shows Error message, Error source, and detailed error dump.
If the record has a key and date, a This key's logs that day button appears top right. It opens the Application logs list filtered by the same key and day. Use this to track the entire flow of an order or customer on that day.
Viewing the payload
The Request, Response, Log content, and Payload tabs use the same viewer:
- If the content is JSON, there are three views: Tree (expandable structure with Expand all and Collapse all buttons), Formatted (indented text), and Raw (as saved). Nested JSON strings are also parsed and shown; select Raw to see the actual text.
- If the content is not JSON, only raw text is shown. If the content looks like JSON but cannot be parsed, a warning appears: The content could not be parsed as JSON; it may have been truncated at the source.
- Enlarge / Shrink changes the height of the viewing area.
- The viewer's own Copy button copies the text in the current view to the clipboard and briefly shows Copied. The Copy button above the card copies the entire payload as saved (raw) and shows Body copied to the clipboard (masked). If the browser denies permission, it shows Could not copy to the clipboard; the browser refused.
For security, sensitive fields in the payload (token, password, cookie, etc.) are masked. If fields are masked, a warning appears above the payload: [number] fields are masked in the body (token, password, cookie, etc.). The copied text is also masked. If the payload is very long, a warning appears: The body was truncated due to length; check the log repository for the full content. If the record has no content, it shows This record has no body; only log names with request/response content save bodies.
Operations
Finding logs for an order
- Switch to the Application logs tab.
- Enter the order number in the Key field.
- If the order is old, expand the Date range (up to 31 days).
- Press Filter and open the record from the list.
- Use the This key's logs that day button in the detail to see other records for the same day.
Finding errors in a specific time range
- Select the Date range in the relevant tab; enter Start time and End time if needed.
- In Application logs, select Error in the Type field; in Platform logs, look for red Type badges in the list.
- Press Filter, open the record, and examine the Bug tab.
Common situations
- The list is empty. When date fields are empty, Platform logs cover only the last 24 hours, Application logs the last 10 days. If the record you seek is older, expand the range. Also check the other source; the two sources do not contain the same records.
- "Time could not be read" warning appears and the list is empty. Enter time in
HH:mmformat with two-digit minutes (e.g.,09:05). - Filters reset when switching tabs. This is expected behavior; filters reset when the view changes.
- The list shows "Something went wrong" error. Ensure the date range does not exceed 31 days. If the problem persists, press Retry and provide the text in the Technical detail section to your system administrator.
- Detail shows "Log service not configured" or "Application logs not configured." This is not a fault; it means the relevant log source is not set up for your workspace. Contact your system administrator.
- Some values do not appear in the payload. Sensitive fields are masked for security and cannot be viewed on screen.