Monitor results analysis in Postman

Introduction

Monitor results analysis helps you check if your API tests run well over time. It shows if your APIs work correctly and if any problems happen.

You want to see if your API is always working as expected during the day.

You need to find out why an API test failed in the last run.

You want to check the performance of your API over several days.

You want to get alerts when your API stops working properly.

You want to share test results with your team automatically.

Syntax

Postman

Monitor results are viewed in the Postman app or web dashboard under the 'Monitors' tab.
You can filter results by date, status (pass/fail), and test names.
You can also export results as JSON or CSV for deeper analysis.

Monitor results include details like test status, response time, and error messages.

You can set up notifications based on monitor results to get alerts.

Examples

This shows how to check monitor results step-by-step in Postman.

Postman

1. Open Postman app or go to https://go.postman.co/monitors
2. Select your monitor from the list
3. View the recent runs with pass/fail status
4. Click a run to see detailed test results and logs

Filtering helps focus on problems quickly.

Postman

Use filters to find failed runs:
- Click 'Filter' button
- Choose 'Status: Failed'
- Review failed tests to find issues

Sample Program

This test script checks if the API response status is 200 and the response time is under 500 milliseconds. When this request runs in a monitor, the results will show if these tests passed or failed.

Postman

// This is a Postman test script example inside a request
pm.test('Status code is 200', () => {
    pm.response.to.have.status(200);
});
pm.test('Response time is less than 500ms', () => {
    pm.expect(pm.response.responseTime).to.be.below(500);
});

Important Notes

Always check monitor results regularly to catch issues early.

Use descriptive test names to understand results easily.

Combine monitor results with logs for better debugging.

Summary

Monitor results analysis helps track API health over time.

You can filter and review test runs to find failures quickly.

Good test scripts make monitor results clear and useful.

Practice

1. What is the main purpose of analyzing Postman monitor results?

easy

A. To create user interface designs

B. To write new API requests

C. To track API health and detect failures over time

D. To deploy applications to servers

Solution

1. Step 1: Understand monitor results role

   Monitor results show how API tests perform over time, highlighting issues.

2. Step 2: Identify main goal of analysis

   Analyzing results helps track API health and find failures quickly.

3. Final Answer:

   To track API health and detect failures over time -> Option C

4. Quick Check:

   Monitor results = API health tracking [OK]

Hint: Monitor results show API health trends over time [OK]

Common Mistakes:

• Confusing monitor results with request creation
• Thinking monitor results are for UI design
• Assuming monitor results deploy apps

2. Which filter option in Postman Monitor results helps you quickly find failed test runs?

easy

A. Sort by request name

B. Sort by creation date

C. Filter by response time

D. Filter by status: Failed

Solution

1. Step 1: Identify filter purpose

   Filtering by status narrows results to specific outcomes like failures.

2. Step 2: Choose filter to find failures

   Filtering by status: Failed shows only failed test runs quickly.

3. Final Answer:

   Filter by status: Failed -> Option D

4. Quick Check:

   Status filter = find failures fast [OK]

Hint: Use status filter to isolate failures fast [OK]

Common Mistakes:

• Sorting by request name does not isolate failures
• Filtering by response time shows speed, not failures
• Sorting by creation date orders runs but doesn't filter failures

3. Given this Postman monitor result snippet:

{"runId":123, "status":"failed", "tests": {"responseCodeCheck": false, "bodyCheck": true}}

Which test failed in this run?

medium

A. bodyCheck

B. responseCodeCheck

C. Both tests passed

D. No tests were run

Solution

1. Step 1: Read test results in JSON

   The tests object shows responseCodeCheck: false and bodyCheck: true.

2. Step 2: Interpret boolean test results

   false means test failed, true means test passed.

3. Final Answer:

   responseCodeCheck -> Option B

4. Quick Check:

   False test = failure [OK]

Hint: False test result means failure [OK]

Common Mistakes:

• Assuming true means failure
• Ignoring test result booleans
• Confusing test names

4. You notice your Postman monitor shows all runs as "passed" but your API is down. What is the most likely cause?

medium

A. Test scripts do not check API response status codes

B. Monitor is not scheduled to run

C. API is running but returning errors

D. Monitor results are delayed by 24 hours

Solution

1. Step 1: Analyze monitor showing all passes

   If monitor shows all passes but API is down, tests likely miss failure detection.

2. Step 2: Identify missing test checks

   Not checking response status codes means failures go unnoticed.

3. Final Answer:

   Test scripts do not check API response status codes -> Option A

4. Quick Check:

   Missing status checks = false passes [OK]

Hint: Check if tests verify response status codes [OK]

Common Mistakes:

• Assuming monitor is not running without checking
• Thinking API is up despite errors
• Believing monitor results delay causes issue

5. You want to create a Postman monitor report that highlights only failed tests with response times over 2 seconds. Which approach best achieves this?

hard

A. Filter monitor results by status: Failed and response time > 2000ms

B. Sort monitor results by response time ascending

C. Filter monitor results by status: Passed only

D. Export results and manually check response times

Solution

1. Step 1: Understand filtering needs

   You want to see only failed tests with slow response times.

2. Step 2: Apply combined filters

   Filtering by status: Failed and response time > 2000ms shows exactly those runs.

3. Final Answer:

   Filter monitor results by status: Failed and response time > 2000ms -> Option A

4. Quick Check:

   Combined filters = precise failure + slow tests [OK]

Hint: Use combined filters for precise monitor analysis [OK]

Common Mistakes:

• Sorting alone does not filter failures
• Filtering by passed misses failures
• Manual checks waste time and risk errors