Troubleshoot monitors in Postman

If you encounter a problem with a collection-based monitor, the following troubleshooting steps may help you identify and resolve the issue.

Viewing failed monitors

The Console Log can help you debug issues you might encounter with your collection-based monitors.

1. Go to your workspace and select Monitors in the sidebar.
2. Select a monitor, and then select a failed monitor run in the performance graph.
3. Select Console Log to view monitor run details, along with any console.log() statements you included in your pre-request and test scripts.

For more information on debugging with the Postman Console, see Troubleshooting API requests.

Debugging local run attempts

• Run the failing monitor's collection with its environment in Postman or Newman to see if it's working.

• If a local run passes, check that sync is working by looking for the sync symbol on the left side of Postman's footer. This will ensure any local changes persist.

  

Debugging variable issues

• Ensure that the same environment is used across local runs and monitor runs. To confirm, add console.log(environment); to your request scripts and compare the results across monitoring and local runs.
• If your collection run depends on a saved global variable, change it to an environment variable. Saved global variables aren't supported in monitors.

Logging relevant information

• Unexpected response bodies or header values can be a source of monitor issues. You can log these with the following code:

  console.log(JSON.stringify(responseBody, null, 2));
  console.log(JSON.stringify(responseHeaders, null, 2));
  

Uncaught errors

• Wrapping suspicious code in a try - catch block will enable the test and pre-request scripts in your collection run to completion.