Start free trial

Central data platform for your serverless environment.

Get full access to all premium features for 14 days. No code changes and no credit card required.

Password: 8+ characters, at least one upper case letter, one lower case letter, and one numeric digit

By signing up, you agree to our Privacy policy and
Terms and Conditions.

Lambda: Application Objects

Dashbird continuously monitors and analyses your serverless applications to ensure reliability, cost and performance optimisation and alignment with the Well Architected Framework.

Product Features Start Free Trial

Overview

Logging application objects from a Lambda function code can be useful in a variety of cases:

  • Being able to identify every contextual information involved in a possible application failure
  • Check data points that might have been exposed in a security breach
  • What was the state of a given object before and after a certain action was executed

How-to

As discussed in the AWS Lambda Programming Model1 page, AWS Lambda logs are stored in CloudWatch Logs. It can automatically detect a JSON string and format it for easy visualization in the AWS Console.

External debugging platforms – such as Dashbird – will offer enhanced visualization for JSON strings, with support to expand and collapse object nodes.

For that reason, it is recommended to create a JSON-serializable version of all relevant objects and classes in the code. This way they can be easily logged and inspected in any debugging tool. Having a method for JSON-serialization (e.g. object.to_json()) would be ideal to standardize the implementation across the application functions.


Footnotes


  1. AWS Lambda Programming Model ↩︎

No results found