A monitor lets you run a collection periodically to check for its performance and response. You can set up a monitor to run as frequently as 5 minutes to check if all the requests in your collection are up and healthy.
When you set up a monitor, Postman servers will hit the endpoints in your collection according to the specified frequency. You can also select a corresponding environment to use and store variables. If you have written tests for your requests , the monitor would run these tests to validate the response and notify you when a test fails. You can configure how to receive the alerts from a wide number of integrations available.
Each Postman user gets 1,000 monitoring calls for free per month. Each Postman Pro and Enterprise team gets 10,000 free monthly requests, and it takes only 2 minutes to set up a monitor. Learn more about monitor pricing and getting started with monitors.
There are a few minor differences between running collections in a Postman monitor as compared to using the Postman app collection runner. If your collection relies on any of these features, then it may not work the same way in Postman monitors that it does in the Postman app.
localhostand might encounter a firewall because monitors run in the Postman cloud.
Monitoring resources across multiple regions provides useful information about the status and response time for your endpoints. If you’ve implemented a solution by setting up multiple servers running on multiple continents, then you want to make sure your endpoints are healthy and that none of your users are experiencing unusual delays.
Postman supports monitoring in all 16 geographic regions around the world, operated by AWS Global Infrastructure. If you’re interested in a region that’s not listed in the Postman interface, contact us at firstname.lastname@example.org or through the chat box on the monitors page.
Monitors are priced per request made, with some free requests included every month. Learn more about pricing for Monitors.