In correct User count reported in Admin Sutdio
Hi,
We are using Pega 8.5 version, we observed the Pega Admin Studio shows in correct users count in our production, where as the production users are less. we see sometimes the user count spikes on each server and reaches to 3000 +, this is not correct for our production user base we support. Can you please suggest what could be the problem here? where Can I start my investigation?
Thanks,
Shaik
Updated: 3 Jan 2023 8:02 EST
Pegasystems Inc.
GB
Do you see the status of those inactive requestors as disconnected?
Kindly verify if pyClusterAndDBCleaner Job scheduler is up and running fine?
Are you carrying out any uneccessary health check so every hit as per pega design may be creating none requestors? Although there may be no issue on user session or log out any uneccessary URL hit would generate requestor.
Please review below doc for details about health check- https://docs.pega.com/pega-services-troubleshooting/pega-ping-service-faqs
To use the url for health check status: Seee Pega Ping service FAQs
OTHER CHECKS:
Do you have timeout/requestor/shortlived either in prconfig or DSS?
Batch and APP requestors are created and not removed after work, but eventually they seems to be reused and this is expected behavior. They are kept by particular node in memory to be reused (just for better performance). Only way to remove them is to take down the node.
Also depending on your user's configuration you may have configured the system to support a large requestor count .
Do you have below settings present either in DSS or prconfig?
Initialization/PersistRequestor Timeout/browser
Do you see the status of those inactive requestors as disconnected?
Kindly verify if pyClusterAndDBCleaner Job scheduler is up and running fine?
Are you carrying out any uneccessary health check so every hit as per pega design may be creating none requestors? Although there may be no issue on user session or log out any uneccessary URL hit would generate requestor.
Please review below doc for details about health check- https://docs.pega.com/pega-services-troubleshooting/pega-ping-service-faqs
To use the url for health check status: Seee Pega Ping service FAQs
OTHER CHECKS:
Do you have timeout/requestor/shortlived either in prconfig or DSS?
Batch and APP requestors are created and not removed after work, but eventually they seems to be reused and this is expected behavior. They are kept by particular node in memory to be reused (just for better performance). Only way to remove them is to take down the node.
Also depending on your user's configuration you may have configured the system to support a large requestor count .
Do you have below settings present either in DSS or prconfig?
Initialization/PersistRequestor Timeout/browser
Below are the type of the requestor we see in Requestor management page in admin studio.
APP: When an external system accesses PRPC to get the required information, Pega creates them as a requestor of type APP.Requestor ID for these types of requestors starts with the letter A. Typical examples could be a service call made from an external system to Pega.
Browser: When we access Pega through web browsers, Pega creates them as a requestor of type Browser. Requestor ID for these types of requestors starts with the letter H. Typical examples could be a developer, end-user logging into the application.
Batch: When Pega creates a request by itself on a specific event to execute a set of pre-defined tasks, Pega creates them as a requestor of type Batch. Requestor ID for these types of requestors starts with letter B. Typical examples could be Agents, Listeners configured in Pega, etc..
More details on requestor can be found on https://docs.pega.com/system-administration/85/managing-requestors
Please could you take a look at suggestions given in the support document Operator Presence troubleshooting FAQs and Session Management Troubleshooting FAQs?
LTIMindtree
SA
Is the issue remains the same even after following the MarijeSchillern instructions? if yes, please elaborate.