Monitor usage and its troubleshooting in postman

Viewing monitor usage

The maximum number of monitoring API calls you can make monthly depends on your Postman plan.

• Select team> Resource Usage to open the dashboard to check your team's current monitoring usage. 
   
• For a detailed breakdown, select View detailed usage (under Monitoring Usage) to go to the Monitoring Usage Details dashboard.
   

The Monitoring Usage Details dashboard shows your team's current billing period, how many monitoring API calls have been made, and which monitors have run. The dashboard also identifies monitors by name, creator, collection, and environment.

Monitoring usage details dashboard

If you are concerned about overages, you can go to your Monitoring usage details dashboard for a list of your team's active monitors in one place. You will also find information to help you and your team make informed decisions on monitoring frequency.

How Postman calculates monitor usage

Monitor usage is calculated based on the number of monitoring API calls:

• Running one request (calling an API endpoint) in one region counts as one monitoring API call.
• If the collection monitor uses multiple requests, each request in the collection counts as one API call.
• If the monitor is scheduled to run in multiple regions, each request made in a different region counts as an API call.

Allowing monitor overages

With a free Postman account, once you've reached your monthly usage limit, your monitors are automatically paused for the rest of the billing period. To continue to use monitoring for the remainder of the billing period, upgrade your Postman plan.

Allowing monitoring overages is an option with a premium Postman account. Your monitors keep running after you've used up your monthly allotment of usage credit, and you're charged per monitoring API call at a pay-as-you-go rate.

For paid Postman accounts, overages are permitted by default. Open the Resource Usage dashboard by choosing team> Resource Usage, then turn off Allow monitoring overages to prevent overages.

Purchasing monitoring blocks

Instead of paying for overages after reaching your monthly usage limit, you have the option to purchase additional blocks of monitoring calls. Purchasing blocks may offer savings compared to the pay-as-you-go rate, depending on the number of monitoring calls your team makes.

To purchase additional monitoring call blocks:

1. Select Team > Resource Usage.
    
2. Under Monitoring Usage, select View detailed usage to open the Monitoring usage details dashboard.
    
3. Select Set monitoring block count.
    
4. Select monitoring and enter the number of blocks to purchase.
    
5. Select Review Changes to complete your purchase.
    

Unused monitoring calls or blocks expire at the end of the billing period and do not roll over to the next month.

Monitor activity limits

Postman maintains default limits on various team and user actions to ensure the overall performance and availability of monitoring. Postman will email your Team Admins if your team encounters these limits. In addition, team members will get an alert in Postman.

Postman maintains the following monitoring limits per team:

• Maximum number of active and paused monitors: 300
   
• Maximum parallel runs of all monitors: 500
   
• Maximum parallel runs of a single monitor: 200

Troubleshooting monitors

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 Postman Console log can help you debug issues you might encounter with your collection-based monitors. To view the log:

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 and any console.log() statements you included in your pre-request and test scripts.
    

Viewing failed monitors

Debugging local run attempts

• Run the failing monitor's collection with its environment in Postman or Newman to see if it works correctly.
• 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.

Checking if sync is working or not

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 are not 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 to run to completion.

Frequently Asked Questions

What is a collection in Postman?

In Postman, a collection is used to group related requests. It facilitates organizing requests into folders in a systematic manner.

What kinds of requests can you make with Postman?

Request Method, Request URL, Request Headers, Request Body, Pre-request Script, and Tests are all included in an HTTP request method.

What does Postman's endpoint mean?

You may include Postman in your development toolchain by integrating it with the Postman API endpoints. Through the API, you can add and run monitors, update environments, add and run new collections, and update existing collections. You can now access data kept in your Postman account programmatically.

What does Postman's collection mean?

A collection of saved requests is called a Postman Collection. Every request you make in Postman is recorded in the sidebar's History tab.

Conclusion

We hope this blog has helped you enhance your Knowledge about Postman and its monitor usage along with its various troubleshooting in Postman 3.0

See Basics of C++ with Data Structure, DBMS, Operating System by Coding Ninjas, and keep practicing on our platform Coding Ninjas Studio.

If you think you are ready for the tech giants company, check out the mock test series on code studio.

You can also refer to our Guided Path on Coding Ninjas Studio to upskill yourself in domains like Data Structures and Algorithms, Competitive Programming, Aptitude, and many more! You can also prepare for tech giants companies like Amazon, Microsoft, Uber, etc., by looking for the questions asked by them in recent interviews. If you want to prepare for placements, refer to the interview bundle. If you are nervous about your interviews, you can see interview experiences to get ideas about these companies' questions.

Nevertheless, you may consider our premium courses to give your career an edge over others!

Do upvote our blogs if you find them helpful and engaging!

Happy Learning!