# CloudWatch alarm: Kinesis GetRecords.Success

CloudWatch alarms · Updated 16 November 2026

**Short answer:** Alarm on AWS/Kinesis GetRecords.Success per StreamName with the Average over 60 seconds, firing when it is below your threshold for 5 of 5 minutes. The Average is the fraction of GetRecords calls that succeeded, so a threshold such as 0.95 means "alert if more than 5% of reads fail for five minutes".

## What the metric measures

Every `GetRecords` call on the stream records a 1 if it succeeded and a 0 if it failed. Averaging those values gives a success ratio between 0 and 1. This is a stream-level view of how healthy your consumers' reads are.

A failed call returns no data. By far the most common failure is `ProvisionedThroughputExceededException`: each shard allows five `GetRecords` calls per second and 2 MB/s of reads, shared among every consumer that does not use enhanced fan-out. Add a second or third application reading the same stream and the limits are hit quickly. Other failures include expired shard iterators and permission errors after an IAM change.

## Recommended alarm settings

| Setting | Recommended value |
|---|---|
| Namespace | `AWS/Kinesis` |
| Metric | `GetRecords.Success` |
| Dimensions | StreamName |
| Statistic | Average |
| Threshold | Depends on your situation (a success ratio between 0 and 1; see below) |
| Period | 60 seconds |
| Datapoints to alarm | 5 |
| Evaluation periods | 5 |
| Comparison operator | `LessThanThreshold` |

## Choosing the threshold

Because SDKs and the KCL retry failed reads, a few failures are routine. The threshold should catch a failure rate your consumers cannot absorb by retrying.

1. Chart the metric with the Average statistic at one-minute resolution over two weeks.
2. Note the lowest values seen during normal operation, including deploys and traffic peaks.
3. Set the threshold a little below that floor. If normal minutes never drop below 0.99, a threshold of 0.95 is quiet and still sensitive.
4. If you run several consumers on shared throughput, expect a lower normal floor, and fix that rather than lowering the threshold.

Set missing data to `breaching` if a consumer should always be reading; with no calls there is no datapoint, and an idle stream otherwise looks healthy.

## Create the alarm

```
aws cloudwatch put-metric-alarm \
  --alarm-name kinesis-orders-getrecords-success \
  --alarm-description "Less than 95% of GetRecords calls on orders succeeding" \
  --namespace AWS/Kinesis \
  --metric-name GetRecords.Success \
  --dimensions Name=StreamName,Value=orders \
  --statistic Average \
  --period 60 \
  --evaluation-periods 5 \
  --datapoints-to-alarm 5 \
  --threshold 0.95 \
  --comparison-operator LessThanThreshold \
  --alarm-actions arn:aws:sns:eu-west-2:123456789012:oncall-alerts
```

0.95 is an example; derive yours with the method above.

## When it fires

1. **Check read throttling** on the same stream: if [ReadProvisionedThroughputExceeded](https://cloudconsole.dev/alarms/kinesis-readprovisionedthroughputexceeded) rose at the same time, the cause is capacity.
2. **Count consumers.** Each extra shared-throughput consumer takes a share of the per-shard limits. Move heavy readers to enhanced fan-out, which gives each registered consumer its own throughput.
3. **Look at consumer logs** for the exception names. Expired iterators point to consumers pausing too long between calls; access denied points to a role or key policy change.
4. **Reduce call rate** if consumers poll in a tight loop with tiny batches; ask for more records per call and back off on empty results.

## Questions

### Why is GetRecords.Success below 1 when consumers seem fine?

Throttled calls are retried automatically, so the application may not notice. A small number of failures is normal; a sustained drop is the signal.

### How many consumers can share a Kinesis stream?

Any number can read, but shared-throughput consumers split each shard's read limits. For more than a couple of consumers, enhanced fan-out avoids contention.

## When this happens away from your desk

A drop in read success is easy to dismiss when it is only throttling, until the consumer starts falling behind. CloudConsole is a phone app for AWS, built to show related stream alarms together on your phone.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Recommended alarms (Amazon CloudWatch User Guide)](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.html)
- [Monitoring Kinesis Data Streams with Amazon CloudWatch](https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.html)
- [Kinesis Data Streams quotas and limits](https://docs.aws.amazon.com/streams/latest/dev/service-sizes-and-limits.html)

## Related

- [CloudWatch alarm: Kinesis ReadProvisionedThroughputExceeded](https://cloudconsole.dev/alarms/kinesis-readprovisionedthroughputexceeded)
- [CloudWatch alarm: Kinesis GetRecords.IteratorAgeMilliseconds](https://cloudconsole.dev/alarms/kinesis-getrecords-iteratoragemilliseconds)
- [CloudWatch alarm: Kinesis SubscribeToShardEvent.MillisBehindLatest](https://cloudconsole.dev/alarms/kinesis-subscribetoshardevent-millisbehindlatest)
- [ThrottlingException: Rate exceeded](https://cloudconsole.dev/errors/throttlingexception-rate-exceeded)
- [aws cloudwatch put-metric-alarm](https://cloudconsole.dev/cli/cloudwatch-put-metric-alarm)
- [CloudWatch alarm: Kinesis PutRecord.Success](https://cloudconsole.dev/alarms/kinesis-putrecord-success)

---

Source: https://cloudconsole.dev/alarms/kinesis-getrecords-success

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
