Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Kinesis metrics**: GetRecords.IteratorAgeMilliseconds (lag—critical; target <1 min for real-time); IncomingBytes, IncomingRecords; PutRecord success/failure. **Lambda (consumer)**: Duration, Errors, Throttles, ConcurrentExecutions. **End-to-end**: IteratorAge indicates...
Kinesis metrics: GetRecords.IteratorAgeMilliseconds (lag—critical; target <1 min for real-time); IncomingBytes, IncomingRecords; PutRecord success/failure. Lambda (consumer): Duration, Errors, Throttles, ConcurrentExecutions. End-to-end: IteratorAge indicates consumer lag—if growing, consumers can't keep up. Alarms: IteratorAge > 60 sec; Errors > 0; Throttles > 0. Dashboard: Lag, throughput (bytes/records per sec), error rate, Lambda duration. Best practice: IteratorAge is the key SLA metric; set alarm and runbook.
Pro-Move: 'We alarm on IteratorAge > 30s—caught a consumer bug that caused 10min lag before downstream SLA breach.' Red Flag: Not tracking IteratorAge—you can't know if you're meeting latency SLA.
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.