Lambda Resource

Lambda is a serverless computing service provided by Amazon Web Services (AWS). It allows you to run code scalably and reliably without needing to provision or manage servers. With Lambda, you can create functions that are triggered by events, such as changes to S3 buckets, updates to DynamoDB tables, messages received in the SQS queue service, and more. Each function runs in an isolated environment and automatically scales according to demand, eliminating the need for manual scaling. Additionally, Lambda supports multiple programming languages, including Python, Node.js, Java, C#, and Go, allowing you to choose the language you prefer. With its flexibility and scalability, Lambda is widely used for building microservices architectures, processing real-time events, creating serverless APIs, and automating tasks, making application development more agile and efficient.

How to monitor Lambda on One Platform

1 – In the side menu, click on Services Hub



2 – In the Serverless category, click on the Lambda card



3 – You will be directed to the AWS Lambda configuration form, fill in the fields



4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings



5 – Click on CREATE MONITORING 


Lambda is a serverless computing service provided by Amazon Web Services (AWS). It allows you to run code scalably and reliably without needing to provision or manage servers. With Lambda, you can create functions that are triggered by events, such as changes to S3 buckets, updates to DynamoDB tables, messages received in the SQS queue service, and more. Each function runs in an isolated environment and automatically scales according to demand, eliminating the need for manual scaling. Additionally, Lambda supports multiple programming languages, including Python, Node.js, Java, C#, and Go, allowing you to choose the language you prefer. With its flexibility and scalability, Lambda is widely used for building microservices architectures, processing real-time events, creating serverless APIs, and automating tasks, making application development more agile and efficient.

How to monitor Lambda on One Platform

1 – In the side menu, click on Services Hub



2 – In the Serverless category, click on the Lambda card



3 – You will be directed to the AWS Lambda configuration form, fill in the fields



4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings



5 – Click on CREATE MONITORING