• The Log Viewer provides a comprehensive set of features for viewing and managing logs. Logs can be required by the marketplace, ERP, Webshops, brand.coms, POS systems for troubleshooting any issues.
• The logs can be searched based on various parameters such as Client, Channel, Request Name, From Date, To Date, Request Body, Headers, Status, HTTP Status, and URI.
• Users can expand log results and copy, download, or generate a link for a specific log.
• Additionally, they can configure displayable columns, manage page size, and download all logs. The ELK Log UI Requirements provide details about fetching the list of client IDs and fetching the logs from ELK.

Granting access to view logs

Please follow the below steps for granting the view logs access to the user:

Go to Manage users

If the user already exists, search for the user's name.

In Role Management, choose the application as log.

• Give Role log.viewer for enabling logging access to the user.

Next, go to the home page and choose the Log Application. The below window reflects.

Searching the Logs

The logs can be searched based on the following parameters:

Mandatory Fields

1. Client: Select the OMS client Name from drop down.
2. Channel: This specifies the channel for which the logs are required. Channels can represent ERP, Marketplace, POS or External Fulfillment System.
3. Request Name: For users looking to find logs related to specific requests, this field allows the input of the request name. If the exact name is unknown or if a broader search is desired, an asterisk (*) can be used as a wildcard character to include all possible matches.
4. From Date and To Date: These parameters define the temporal boundaries of your search. "From Date" is the starting point of the time range, while "To Date" marks its conclusion. Together, they allow users to search for logs within a specific timeframe, which is particularly useful for troubleshooting issues or analyzing events that occurred during a particular period.

Non-Mandatory Fields

1. Request Body: Although optional, this field can be used to search for logs that contain specific information within the request body. It's useful for detailed analyses or when looking for logs that match certain criteria within the request content.
2. Headers: Searching by headers can help in identifying logs that came with specific header information. This is useful for debugging or verifying that the correct headers were used in requests.