Postman Monitor logs lacking per-request timestamps

Postman Monitors are utilized to track API health by executing scheduled requests and recording response bodies and status codes. This functionality is critical for diagnosing deployment failures by correlating API outages with CI/CD pipeline events.

While the Monitor UI provides a high-level status for each run, there is a lack of granular, per-request timestamps within the execution logs. This creates uncertainty when a single monitor contains multiple requests, as it becomes difficult to align a specific failed request with the exact second a deployment occurred.

• How can per-request timestamps be extracted for a specific monitor run to ensure precise alignment with deployment logs?
• Does the Postman API provide more granular timing data for individual requests within a monitor run than what is visible in the UI?