Analytics
Welcome to PruTAN's Analytics dashboard. This comprehensive feature provides detailed metrics and actionable insights for Hostbox and Interceptor module APIs. Leverage these analytics to monitor system performance, track data flow, diagnose issues, and optimize your API testing and transformation workflows.
The Analytics feature delivers a holistic view of simulated request performance, encompassing data transformations, logging mechanisms, and performance indicators.
Hostbox Analytics
Interceptor Analytics
Key Metrics
- Timestamp: The exact date and time when the request was executed, enabling chronological tracking of API interactions and performance over time.
- Request: The complete payload of the API request that is executed, including all parameters, headers, and body data sent to the server.
- Response: The initial response payload received from the server before any transformation rules are applied, providing the raw server output.
- Rules: Custom scripts or logic implemented to modify or transform the response data, allowing for dynamic adjustments based on specific conditions.
- Request Rule: Scripts designed to update or modify the client request body within the Interceptor module, facilitating pre-processing of outgoing requests.
- Request After Rule: The modified request payload after the application of transformation rules, showing how the original request has been altered.
- Response Rule: Scripts used to modify the final response received by the user, enabling post-processing of server responses for enhanced functionality.
- Response After Rule: The final response payload delivered to the user after all rules and transformations have been applied, representing the end result.
- Logs: Detailed logs containing raw response data, print statements, and system-generated messages that aid in debugging and monitoring execution flow.
- Headers: Comprehensive list of HTTP response headers that provide essential metadata about the API response and server configuration.
- Status Code: The HTTP status code returned in the response, indicating success or failure (e.g., 200 for OK, 404 for Not Found, 500 for Internal Server Error).
- Execution Time: The total time taken to process and complete the request, measured in milliseconds, crucial for identifying performance bottlenecks.
- Size: The total size of the response payload, measured in bytes or kilobytes, important for assessing bandwidth usage and optimization needs.
Analytics Report
If there is a need to share the details You can also generate a PDF report of the certified analytics data of request executions.
- Clear button removes the selected scripts.
Steps to genearte Analytics Report :
- Go to the Analytics submenu in the application.
- Select the desired folder, then choose the corresponding request node.
- Hover over the execution details — a checkbox will appear on the right side of each record.
- Select one or more execution details that you want to include in the report.
- Click the View Report button at the top-right corner to open the report dialog box.
- Click the Generate button to create the report. A PDF report will be downloaded available for viewing.