Question
Anthem
US
Last activity: 29 Jan 2020 9:56 EST
How to pull user counts for those users who doesn’t generate any logs ?
Hi Team,
We have a requirement to grab user counts from all JVM's/Nodes on periodic basis.I have evaluated the following options 1)Ping Service (caused DB degradation) 2) AES (Caveat : Sum count of all requestors can be obtained which includes Browser,Batch,Portal and Application) 3)Launch the individual SMA URL's (hectic) 4)Cluster Management Landing Page (not applicable as we cannot login into the dev portals @ production).
None of the above mentioned works out for us.
Please suggest regarding below :
1)Using Splunk, we can only pull the Users count who are making interactions, but there won’t be any visibility of other Users who doesn’t generate any logs. (like managers who are transferring the workbasket items to individual users or who just researches past calls to make a report etc.).Any idea ?
2) SQL query to pull the browser requestor count every hour.
Thank you.
Proximus
BE
Hello,
Can you make a code change at login time to record who's logging in and to which node?
Then, implement something similar when user logs out or timeout?
From AES DB, you could maybe have a look at
select * from AES_SCHEMA.PEGAAM_PERF_STATS t
where t.pxrequestortype='BROWSER'
and t.clustername='YourCluster'
and to_date(t.pxsnapshottime) >= trunc(sysdate)
If you take a snapshot every X min, you should be capable to make a global view on your system usage I think. I'm not familiar to this table but it seems you could find some relevant data for your report.
Hope this helps
Regards
Anthony
Anthem
US
Hi Anthony,
Please find the inline comments below.
Can you make a code change at login time to record who's logging in and to which node? We do have OOTB log message record available in the logs when we login.
Then, implement something similar when user logs out or timeout?
We don’t have any record in the logs when the user logs out,I have not verified this logic if it is OOTB or customized (just stated current behavior).Bigger risk would be with a user closing the browser without logging off from the portal.