Granting access to view logs

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

Searching the Logs

The logs can be searched based on the following parameters:

Mandatory Fields

1. Client: This parameter is crucial as it identifies the client entity whose logs you are interested in. The client entity name must be accurately provided to ensure the search results are relevant to the specific client in question.

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.

3. Status: This parameter allows for the filtering of logs based on the status of the request. Status can be SUCCESS, FAILURE, or WARNING. It can help in quickly identifying failed requests or requests with warning.

4. HTTP Status: Similar to the Status field, this allows for filtering based on the HTTP status code returned by the request. It's particularly useful for web services troubleshooting, where understanding the nature of HTTP responses (e.g., 200 OK, 404 Not Found) is critical.

5. URI: For searches focused on specific endpoints or resources, the URI parameter can be used to locate logs related to particular URIs. This is beneficial when analyzing the traffic or issues related to specific parts of a service.

Understanding and utilizing these search parameters effectively can significantly enhance your ability to find and analyze the necessary logs, aiding in troubleshooting and analysis.

On click of the Search button, the results are displayed as shown below.

Image Added

Any of the log results can be expanded on click of the request name.

Image Added

When the "more" button is clicked, users can expand the request, response, headers, and other related information.

To copy a particular section such as request, response, headers, etc., simply click on the copy button located at the right end.

Image Added

Copy, Download, or Generate a Link for a specific log

The JSON payload containing all fields can be easily copied using the copy button. Additionally, users have the option to download the payload by clicking on the Download button. Furthermore, there is also an option for users to generate a public link for the specific log.

Image Added

Configure Columns in Log search App Result

Manage Page Size

Page size represents the number of requests displayed on a page. Users can choose 100, 200, or 500.

Image Added

In cases where the number of results exceeds the defined page limit, users can employ the left and right arrows to navigate to the next page.

Image Added

Download All Logs

Click on the Download All Logs button to download all logs. Logs will be downloaded in JSON file on a single page.

Image Added