Hello,

we are currently working on setting up Open messaging in a development instance of Genesys Cloud and are ready for UAT. Looking at our historical (peak) volume, the default rate limits on below endpoints are most probably not high enough. 

• api/v2/conversations/messages/inbound/open
• open.inbound.message.typing.event.rate.per.minute
• open.outbound.message.typing.event.rate.per.minute
• org.app.user.rate.per.minute

Obviously, we prefer to have the correct limits in place before going into production and not hit them in our busiest time of the year.

The endpoint rate limits are configurable, but we need to prove that we need them at a certain level. Does anyone have experience in setting up a load test for open messaging or knows of a tool to do so and to provide evidence of the needed limits to Genesys Support? We'd need at least a couple of hundred concurrent fictional/ test users.

Thanks!

Jeroen

#ArchitectureandDesign
#DigitalChannels
#Implementation
#Integrations

------------------------------
Jeroen van der Sandt
bol.com B.V.
------------------------------

Some limits are expandable and some are not like org.app.user.rate.per.minute.  On the ones that are true for configurable, you can submit a use support case with evidence based on extrapolation of current data to ask for an increase.  The main thing will proof of the upper limit expectation and the impact on the business if you exceed that limit.  For instance, if you say the typing indicator rate will be exceeded when you get 2000 agents on interactions at the same time, how will not seeing a few of those really affect the business.  The support engineer will engage the reliability team and the PM to make the final decision.  

------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
------------------------------

Original Message:
Sent: 03-01-2024 10:05
From: Jeroen van der Sandt
Subject: Load testing an Open messaging implementation

Hello,

we are currently working on setting up Open messaging in a development instance of Genesys Cloud and are ready for UAT. Looking at our historical (peak) volume, the default rate limits on below endpoints are most probably not high enough. 

• api/v2/conversations/messages/inbound/open
• open.inbound.message.typing.event.rate.per.minute
• open.outbound.message.typing.event.rate.per.minute
• org.app.user.rate.per.minute

Obviously, we prefer to have the correct limits in place before going into production and not hit them in our busiest time of the year.

The endpoint rate limits are configurable, but we need to prove that we need them at a certain level. Does anyone have experience in setting up a load test for open messaging or knows of a tool to do so and to provide evidence of the needed limits to Genesys Support? We'd need at least a couple of hundred concurrent fictional/ test users.

Thanks!

Jeroen

#ArchitectureandDesign
#DigitalChannels
#Implementation
#Integrations

------------------------------
Jeroen van der Sandt
bol.com B.V.
------------------------------