This is related new feature, shard level metrics.
$ aws --version
aws-cli/1.10.21 Python/2.7.10 Linux/4.4.5-15.26.amzn1.x86_64 botocore/1.4.12
$ aws kinesis create-stream --stream-name foo --shard-count 1
$ aws kinesis describe-stream --stream-name foo --debug
...
2016-04-20 03:24:40,538 - MainThread - botocore.parsers - DEBUG - Response body:
{"StreamDescription":{"EnhancedMonitoring":[{"ShardLevelMetrics":[]}],"HasMoreShards":false,"RetentionPeriodHours":24,"Shards":[{"HashKeyRange":{"EndingHashKey":"340282366920938463463374607431768211455","StartingHashKey":"0"},"SequenceNumberRange":{"StartingSequenceNumber":"49561203237286696357221491199423707957921949335917953026"},"ShardId":"shardId-000000000000"}],"StreamARN":"arn:aws:kinesis:ap-northeast-1:123456789012:stream/foo","StreamName":"foo","StreamStatus":"ACTIVE"}}
...
2016-04-20 03:24:40,540 - MainThread - awscli.errorhandler - DEBUG - HTTP Response Code: 200
{
"StreamDescription": {
"RetentionPeriodHours": 24,
"StreamStatus": "ACTIVE",
"StreamName": "foo",
"StreamARN": "arn:aws:kinesis:ap-northeast-1:123456789012:stream/foo",
"Shards": [
{
"ShardId": "shardId-000000000000",
"HashKeyRange": {
"EndingHashKey": "340282366920938463463374607431768211455",
"StartingHashKey": "0"
},
"SequenceNumberRange": {
"StartingSequenceNumber": "49561203237286696357221491199423707957921949335917953026"
}
}
]
}
}
$ aws kinesis enable-enhanced-monitoring --stream-name foo --shard-level-metrics ALL
{
"StreamName": "foo",
"CurrentShardLevelMetrics": [],
"DesiredShardLevelMetrics": [
"IncomingBytes",
"OutgoingRecords",
"IteratorAgeMilliseconds",
"IncomingRecords",
"ReadProvisionedThroughputExceeded",
"WriteProvisionedThroughputExceeded",
"OutgoingBytes"
]
}
$ aws kinesis describe-stream --stream-name foo --debug
...
2016-04-20 03:36:21,892 - MainThread - botocore.parsers - DEBUG - Response body:
{"StreamDescription":{"EnhancedMonitoring":[{"ShardLevelMetrics":["IncomingBytes","OutgoingRecords","IteratorAgeMilliseconds","IncomingRecords","ReadProvisionedThroughputExceeded","WriteProvisionedThroughputExceeded","OutgoingBytes"]}],"HasMoreShards":false,"RetentionPeriodHours":24,"Shards":[{"HashKeyRange":{"EndingHashKey":"340282366920938463463374607431768211455","StartingHashKey":"0"},"SequenceNumberRange":{"StartingSequenceNumber":"49561203237286696357221491199423707957921949335917953026"},"ShardId":"shardId-000000000000"}],"StreamARN":"arn:aws:kinesis:ap-northeast-1:123456789012:stream/foo","StreamName":"foo","StreamStatus":"ACTIVE"}}
...
2016-04-20 03:36:21,894 - MainThread - awscli.errorhandler - DEBUG - HTTP Response Code: 200
{
"StreamDescription": {
"RetentionPeriodHours": 24,
"StreamStatus": "ACTIVE",
"StreamName": "foo",
"StreamARN": "arn:aws:kinesis:ap-northeast-1:123456789012:stream/foo",
"Shards": [
{
"ShardId": "shardId-000000000000",
"HashKeyRange": {
"EndingHashKey": "340282366920938463463374607431768211455",
"StartingHashKey": "0"
},
"SequenceNumberRange": {
"StartingSequenceNumber": "49561203237286696357221491199423707957921949335917953026"
}
}
]
}
}
This is related new feature, shard level metrics.
https://aws.amazon.com/blogs/aws/amazon-kinesis-update-amazon-elasticsearch-service-integration-shard-level-metrics-time-based-iterators/
For
describe-streamAPI calls,EnhancedMonitoringis included in the response body, but CLI output does not include them.See the following sessions: