Release Notes - Amazon Kinesis Real-time v2.4.3.2


Highlight

Resolving network traffic encountered by 400 concurrent users by reducing the volume of cache data being sent to messaging api.


Product Enhancement

  • ESD-6802 AWS caching issue under 400 concurrency - Network traffic encountered by 400 concurrent users is due to the high volume of cache data being sent to the messaging api. To reduce this traffic, some of the AgentEvent fields need to be null. This change applies to cache data only, realtime data displays on dashboard as expected.

New config, AgentEventColumnsToSetToNull, can set the cache data of specified AgentEvent columns to null.

AgentEventColumnsToSetToNull- <field name>

This is comma separated for multiple fields.

The following columns cannot be set to null as required in processing AWS RT data:

- AgentArn

- EventTimestamp

- StartTimestamp

- StateTimestamp

- ConnectedToAgentTimestamp

 

No columns set to null

Some columns set to null

After simulating a call