The following are some frequently asked questions you might have about Postman Insights.
Just like Sentry makes it easier to debug certain errors even if you have New Relic, we’re aiming to make it easier to debug API errors even if you have other tools installed.
The short answer is no. The Insights Agent is not a proxy and doesn’t sit in the path of traffic. Instead, the agent passively watches traffic using the Berkeley Packet Filter (BFP). For more information, see Footprint of the Postman Insights Agent.
The Postman Insights Agent takes up about 500 MB of memory. The actual amount of memory depends on the volume of API calls the agent is watching. If you have concerns, please email the Postman Insights team to help you decide if you should increase your memory limits. Coming soon: memory limits on the agent.
For Kubernetes, to the best of our knowledge we’re completely isolated, so we shouldn’t affect your service’s performance or uptime.
For Elastic Beanstalk, the agent shares the same memory pool as the rest of the application, so there’s a chance of running out of memory.
Insights scrubs a set of default fields. For more information, see Repro mode data redactions.
If there are additional values you’d like to scrub, you may specify additional fields, values, and regular expressions to redact in Settings.
If Repro Mode is off, all payloads are obfuscated. For more information, see Repro mode data redactions.
Create a dedicated workspace for your Insights project and make it visible only to the users who are allowed to view the payloads. To learn more about internal workspaces, see Create a workspace in Postman and Manage team resources in Postman.