Postman Monitors do a great job of alerting you to issues, but they stop short of helping manage incidents. That’s where I’ve been experimenting with Postman Flows, building a workflow to address API errors manually or via webhooks.
Detect specific errors like 429 or 503 and categorize them.
Post incidents for tracking and resolution.
This has been a helpful workaround, but it’s manual or Webhook calling and not part of Postman Monitors.
The Idea: Merge Monitors and Incident Management
Imagine if Postman Monitors could:
Automatically log and categorize API errors.
Trigger incident workflows like my Flow does, but seamlessly within Monitors.
Integrate with external tools like Slack or Incident.io for real-time updates.
This would combine the flexibility of Flows with the automation of Monitors, saving time and enabling faster resolution.
Future Scope
With built-in incident management, Postman could become a one-stop solution for API monitoring and resolution ideal for DevOps and SRE teams.
Such a feature would be widely adopted by enterprise users, positioning Postman as an essential tool for reliability and incident management at scale.
Hi @jeanqasaur ,
I have requested postman insight alpha access.
I’ve read through the documentation and found it incredibly insightful. it provided a lot of guidance during installation and setup.
I’ve gone through the following steps to set up Postman Insights:
Installed and configured Minikube on my macOS with Docker as the driver.
Deployed HTTPBin on Kubernetes as a mock API for testing.
Successfully installed the Postman Insights Agent from the Git repository.
Generated traffic on the HTTPBin deployment using curl and Postman.
Completed the injection of the Insights Agent into the HTTPBin deployment.
Currently, I am at the point where I need a Project ID or key to fully connect the agent with my Postman account and start viewing insights in the dashboard.