Closed EYSue closed 1 year ago
Hi @EYSue , Thanks for raising the query. Please give us sometime and will get back to you with proper response soon.
@EYSue ,
_Scaling Issue- the option to opt out of virtual pairings requires database storage and with the current architecture will not scale to a large organisation, Could you please provide information on the user base that your particular team is targeting? What are the specific concerns you have regarding the scaling aspect?
For more info on the pair ups- Go to App insights-->Events--> Choose during like 24 hours/last 60 days as per your requirement-->Sroll to the bottom in the same page-->Under Event statistics, ProcessedPairUps, Usersactivity etc.,-->Here we can more info. Here is one of the references
Is it possible to control the use of Icebreaker using a security group?, Could you please provide what's the use case of security group in your Icebreaker bot.
Thanks Sai, I am meeting with the developer team tomorrow and then I will provide more context.
Sai, these are the specific questions
@EYSue , We noted your points and will discuss with the team internally. We will keep you posted.
@EYSue We have responded to the queries on app architecture internally over mail. Please let us know if any further assistance is required.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
Hi
I looked into deploying Icebreaker at EY several years ago and encountered the following issues.
I now have re-newed interest to deploy this app and would like to know if the architecture remains unchanged and we can still expect scaling issues and also if the multiple team issue is resolved as I believe you were planning to implement a fix for this in a version release.