Product

Elevate Lambda Log Analysis with Edge Delta

We’re thrilled to announce the release of our Lambda Pipeline Pack — a pre-built collection of processors designed to intelligently optimize Lambda log data for enhanced Lambda monitoring and strengthened downstream analysis.

Parthiv Mathur
Feb 28, 2025
1 minutes
Share

See Edge Delta in Action

Serverless architectures are rising again in popularity, with developers increasingly leveraging cloud-based serverless tooling that supports compute, database, workflow automation, and container orchestration functionalities to name a few. AWS’ event-driven Lambda service is one such example, enabling developers to create Lambda functions to run code without provisioning or managing any of the underlying infrastructure themselves. 

The Challenges with Serverless: Lambda and CloudWatch

While simple to use, Lambda functions are essentially black boxes, as they handle all the underlying compute that enables the code to run. To help provide users with visibility, AWS Lambda automatically monitors Lambda functions and generates logs associated with each individual action taken. However, Lambda logs are sent to Amazon CloudWatch by default for analysis, which is an expensive tool — especially at enterprise scale. 

With Edge Delta’s Lambda Extension, Edge Delta users can easily circumvent CloudWatch by shipping Lambda logs directly into an Edge Delta Telemetry Pipeline, from where they can be easily routed to any downstream destination of their choice.

Additionally, with Edge Delta’s Lambda Pipeline Pack, teams can leverage a pre-built collection of processing steps to intelligently optimize and enrich their Lambda logs in stream with ease, keeping insight quality high while significantly reducing log volume and ultimately downstream cost. 

In this blog post, we’ll walk through how the Lambda Pack is architected, what benefits it provides to your Lambda logs, and how to add it into Edge Delta’s pipelines. 

Edge Delta Lambda Pack — Internals, Benefits, and Integration

Before diving into the pack’s internals, let’s cover Edge Delta’s Lambda architecture at a high level:

Our Lambda Extension sits directly within your Lambda environment and forwards Lambda logs to an Edge Delta Cloud Fleet. From there, the logs are processed and forwarded to the destination(s) of your choice, including legacy observability platforms, archival storage, and Edge Delta’s Backend. 

Our Lambda Pack slots seamlessly into your Edge Delta Pipelines, and automatically structures your log data to reduce log volume and enable powerful insights downstream. Here’s how it works:

Parse JSON Attributes

The pack begins by leveraging a Parse JSON Node to isolate the most important pieces of the JSON-formatted log data:

- name: body_attributes
  type: parse_json_attributes
  process_field: item.body

Structure JSON Fields

Once parsed, the logs are then structured via an Extract JSON Node in the {attributes} section of the log item:

- name: extract_message
  type: extract_json_field
  field_path: message
  keep_log_if_failed: true

Once processing is complete, the incoming Lambda log has been optimized, structured, and prepared for further downstream processing and analysis. Here’s an example of how the Lambda pack enriches the log body of a Lambda log:

Log body at ingestion:

  "body": "{"cloud"":{""resource_id"":""arn:aws:lambda:us-east-2:00000000000:function:example-log""

Stay in Touch

Sign up for our newsletter to be the first to know about new articles.