GetRecords Latency Spike From Processing Bottleneck
latency
GetRecords.Latency measures time for each GetRecords operation. High latency indicates consumer processing logic (not network) is the bottleneck. For KCL consumers, this correlates with ProcessTask.Time metric showing slow per-record processing.
Amazon Kinesis insight details requires a free account. Sign in with Google or GitHub to access the full knowledge base.
Sign in to access