AWS Lambda Adds IteratorAge Metric for Improved Processing Operations Visibility

Oliver Berger | Thu, 09 Mar 2017

AWS Lambda just got a bit better thanks to IteratorAge.

If you’ve ever read the GorillaStack blog, you’re likely well-versed on many of AWS Lambda’s many use cases. Of particular interest in the context of Amazon's latest announcement is the way in which the compute service works in tandem with CloudWatch. Lambda can assist in monitoring functions and reporting metrics on your behalf. Up until now, these metrics—time-ordered sets of data points included throttles, DLQ errors, duration, errors, and total invocations.

But the new kid on the block, the IteratorAge metric, shakes up the game and enhances visibility into stream-based processing operations.

IteratorAge is strictly for stream-based invocations and works by determining the age of the last record for each batch of processed records. Age is quantified by measuring the time elapsed between when Lambda received the batch in question and when the final record within that batch was written to the stream.

The ultimate benefit of IteratorAge? Thanks to the delay detection afforded by Lambda’s new latest metric, you can whip up alarms that enable the efficient monitoring of your stream-based operation’s performance.

IteratorAge is available now as a default, free-of-charge metric within Lambda. It can be accessed via Lambda’s console monitoring panel.

Check out more on monitoring AWS Lambda functions. Also, discover Amazon's CloudWatch guide here.

Oh, and want to learn more about efficient monitoring of your cloud-based processes? Contact us here at GorillaStack to discuss how we can save your business money through the savvy automation and optimization of cloud usage, performance and governance.

Tags CloudwatchDevelopmentLambdaTechnologyBack To All Posts