Monitors continuously track the health and performance of your APIs. With Postman, you can stay up to date on what’s happening across all monitors in your workspace. Or you can review individual monitors to examine test results and performance over time.
You can view your monitors in Postman by clicking Services in your workspace and expanding Monitors in the sidebar. Select your monitor to open a tab detailing its latest performance.

Monitors are visible to all members of the workspace.
You can use the monitor summary to understand how your APIs have performed over time. Each monitor run is represented by a bar in the graph. By default, this displays the monitor’s Run summary view.
The upper section charts your monitor’s average response time for each run, while the lower section visualizes the number of failed tests for each run across all regions. To view the exact values for failed percentage and response time, hover over each run individually.

A red bar indicates that either tests failed or errors occurred during the run. For more information, view your Console Log.
You can select Individual requests to break down your monitor summary into separate requests.

You can use filters to identify recurring patterns in your monitoring runs by selecting particular requests, run types, results, and regions (if applicable). Click Clear Filters to return to your original dashboard view.
You can filter by a specific request to compare its response time in different runs.
You can filter by run type to compare how the response time changes between the type of run:
postman monitor run command.Click Clear selected in the dropdown to clear the selected filters.
You can filter by run results to compare how your runs with the same result have differed. Each run is labeled based on its result:
Click Clear selected in the dropdown to clear the selected filters.
You can filter by regions or runners to compare API health or performance across multiple geographic regions or networks.
This feature is available if you selected multiple regions or runners when you created or last edited your monitor.
You can review past run results to understand what happened at a particular point in time. To do so, select Individual requests then click Go to in the graph. Select the time and date, then click Apply to view a specific run.
To revert the view to your most recent runs, select the time and date you defined in the upper-left corner of the graph, then click Reset.
Click All Tests to get more detailed information on your tests, including which passed or failed, the response codes, the response times, and any failed test assertions.

To learn more about the test results for each request, you can view the following:
Click the Errors tab to filter results by requests that encountered errors. Errors indicate runtime issues like timeout or TLS handshake errors. Failed requests occur when one or more user-specified checks (like post-request scripts) don’t match expectations.
The requests in your collection run that have errors appear in the run results page with an error badge and the error message. Badges identify errors as related to network, request, or script issues.
Click the Console Log tab to view and search monitor run details along with the console.log statements that run as part of your pre-request and post-response scripts in the Postman Console. Run details specify the various stages of a monitor run such as preparing run, running, rerunning (if applicable), and the run result, along with error and test failure information. Clicking a request in the console log opens it in a tab, allowing you to review and edit the request as needed.
If your monitor is configured to run in multiple regions, you can select a different region in the Runner menu.

You can use the Console to both troubleshoot issues and learn more about an individual run’s behavior.
Find specific strings with the Console log’s search feature. Searching enables you to highlight and cycle through error messages and codes automatically instead of scanning the log manually.
Matches are highlighted in the log, and you can click Next match and
Previous match to cycle through them. Click
Clear search to clear the search field and results.
Monitor run logs are retained for a period of six months. If you select a monitor run that’s outside the retention period, you can view the number of failed tests and errors. Other monitor run details will no longer be available. To request this information, contact Postman support.
You can view a monitor’s history by clicking History in the sidebar.
You can check these logs to learn when a monitor was created, edited, paused, or resumed running, and which team member performed each action.
You can view details about a monitor by clicking Monitor details in the right sidebar. You can view a monitor’s ID, creator, creation date and time, collection, environment, and integration options.
Learn how to troubleshoot your monitors and check out Postman monitoring FAQs.