활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.
활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.
Hello all,
We have been investigating the possibility of using MongoMK for our Author instances, and have decided to continue using TarMK until we absolutely have to switch. One of the suggested Mongo requirements is if you get above 100 concurrent authors. How can you monitor the number of concurrent authors?
Thank you,
Andrew
해결되었습니다! 솔루션으로 이동.
조회 수
답글
좋아요 수
You can try below commands -------------------------------------------------------------------
To see the number of authors that have used the system since installation use the command line:
cd <cq-installation-dir>/crx-quickstart/logs
cut -d " " -f 3 access.log | sort -u | wc -l
To see the number of authors working on a given date:
grep "<date>" access.log | cut -d " " -f 3 | sort -u | wc -l
조회 수
답글
좋아요 수
Hi Andrew,
Every request in aem is atomic & you need to integrated with any idp (saml...) to get the concurrent monitor validation Or need custom implementation. Other workarounds like /system/console/tokenmgr Or parsing logs really not scale out well from personal implementation experience.
Thanks,
조회 수
답글
좋아요 수
You can try below commands -------------------------------------------------------------------
To see the number of authors that have used the system since installation use the command line:
cd <cq-installation-dir>/crx-quickstart/logs
cut -d " " -f 3 access.log | sort -u | wc -l
To see the number of authors working on a given date:
grep "<date>" access.log | cut -d " " -f 3 | sort -u | wc -l
조회 수
답글
좋아요 수
Thanks - will they scale up to ~100 users okay? We're mostly worried about that threshold in particular
조회 수
답글
좋아요 수
Thanks Sandeep, that actually really helps. It looks like we've only had 80 unique users in the last week, and the highest was 58 in one day. It's safe to say we're under the 100 concurrent user threshold. We'll have to look into better ways to watch concurrent users.
조회 수
답글
좋아요 수