@GuiValino1984 requestor pooling helps manage system load by reusing requestors, but when transaction volumes spike, it can lead to service issues. While Pega doesn't provide an OOTB way to view the history of requestor pools over time, there are several ways to monitor this behavior. You can enable requestor tracing or logging to capture details during high traffic periods, though this won't give historical data. The Performance Management tool offers some metrics, but it's not detailed enough for specific service packages. A custom solution can track requestor usage by logging when requestors are checked out or returned to the pool. You can also review system logs for performance issues or create custom reports using the PRRequestor table to analyze usage patterns. Integrating third-party monitoring tools can give you better insights into requestor behavior and performance trends over time. Fine-tuning your requestor pool settings and setting up alerts can also help avoid overloads during peak times.