Posted: 28 Oct 2016 14:38 EDT Last activity: 21 Dec 2016 11:05 EST
Service Invocation count increase after upgrade to PEGA 7.1.6
I am looking at the service invocation count and it jumps about 50% the same month we upgrade from PEGA 5.4 SP2 to PEGA 7.1.6. Why would this happen and where is the data for the table 'PR_HOURLY_USAGE' pulled from? Is this data available for me to look at?
***Updated by Moderator: Maryrita to move from Pega 7 Upgrade Center to Product Support Community***
***Updated by Moderator: Marissa to update categories***Lochan: Added SR details***
The difference in architecture between PRPC 5.x and Pega 7 is substantial. This alone could certainly have lead to what you are seeing. With that said, we can look a little deeper. Are you seeing this in production under similar load to what was in PRPC 5.x? Any indication which requestor types are impacted?
You can use pr_hourly_usage in tracking historical data. "You can use pr_perf_stats, pr_daily_usage and pr_hourly_usage table in order to get number of users/requestor logging in Daily/Hourly. These tables have all the details related to request login and logout information. By querying pr_hourly_usage you can get a pattern of number of concurrent request logging in a particular hour."
Mark is out of the office, so I am replying instead. We are seeing similar workloads within Production but the increase in invocations was in the neighborhood of a 60% increase upon switching. I had a sales rep mention to ensure that we have our reg/occ users setup properly. Is there some guidance that can be provided on what to look for within a user account that would make them show as an invocations instead of a user? As an additional note, the we queried the PR_Hourly_Usage table but the numbers generated by the OverallSystemUsage_All report do not match. I feel we are missing a critical piece somewhere.
I see that this SR is being worked on. However, I did not see any mention of this post in the SR Notes. I have added a Pulse post with the URL of this post on the SR for effective troubleshooting. I have updated your post above for the SR details and will continue to track it!