All Collections
Portal-X Pages
User | Summary | Logs
User | Summary | Logs

View recent client requests and responses

Jason Liang avatar
Written by Jason Liang
Updated over a week ago

This page shows any recent API requests and responses invoked by an individual end user in your current application. User logs are useful as a valuable resource for debugging during the process of application development, as well as for monitoring user activity during maintenance periods. Through this page, you can

  • View the recent API requests and responses invoked by the selected end-user in detail.

  • Export the recent user logs into a .json file for further analytical or debugging purposes.

You can now see all the selected User’s recent requests and responses sorted by most recent.

  • Date/Time – The time and date that the request was issued by the User.

  • Packet ID – The packet ID increments with each request the User makes. By clicking the eye icon to the right of the ID you can view the raw request information that was sent to the server.

  • Session ID – A unique ID created every time the User authenticates and persists until they re-authenticate, log out, or their session expires from inactivity.

  • Request(service OPERATION) – The API operation contained in the call in the format (serviceName OPERATION_NAME).

  • Response – The response code issued by the server. Anything other than 200 indicates an error was returned. Like with the Packet ID, clicking the eye to the right of the response will open a window containing the raw data returned in the response.

Sometimes you may see multiple Requests in a single Packet. The client will often bundle multiple requests into one Packet when they are issued very close together. The result is visible in the logs as a Packet with multiple Requests. In this case, the Response is also bundled before it’s returned to the client.

Click an individual log entry from the list to access the details of the chosen log request and response data.

You can click the Export button to export the log data into a .json file for analytical or debugging purposes.

Did this answer your question?