The key to effective Lambda monitoring is combining the three pillars of observability - metrics, logs and traces - in a single place for the full context and details that enable fast root cause analysis.
Helios offers a wide range of deployment, observability & troubleshooting capabilities for AWS Lambda and other serverless functions.
- Deployment manually, through a Lambda layer or even a serverless plugin
- Observability & monitoring based on both the instrumented traces & metrics, as well as the raw logs from AWS
- Troubleshooting all errors - applicative or not - made simpler based on E2E traces and context propagated properly
Install the Helios SDK in your services by leveraging any of the supported deployment options:
- Using Helios' Lambda layers - the most updated version is available under Settings > General in the Helios app (Recommended)
- Configuring Helios' serverless plugins
- Manually setting environment variables in Lambda configuration (Go | Node.js | Python)
AWS integration is required in order to get the complete Lambda observability & monitoring capabilities
Each Lambda, represented as its own service in Helios, also provides a Lambda overview. It includes various trends & stats on metrics such as error trends, invocations, etc.
This Lambda status page provides a snapshot of what's going with the Lambdas used, across all regions. For each function and within the time frame selected it displays the last invocation, number of invocations, number of function errors, number of OOMs, number of timeouts, average duration, and also account ID, region and ARN. It is available under Cloud entities > Lambda.
To enable quicker troubleshooting and access to the full context of the invocations and errors - there are also links to the relevant traces in Helios so you can easily see E2E flows.
Gaining intuitive visibility into an end-to-end flow with your Lambda functions is possible leveraging Helios' OpenTelemetry SDK and showing the data and appropriate context.
Users can customize and control exactly what data is important to them with each Lambda by leveraging the labels & alerts in Helios to save search queries and detect behaviors that are of interest. Customization can be done based on either applicative events, or Lambda metrics from AWS.
For each span it's possible to retrieve the relevant logs from CloudWatch with a short click of a button.
Similar to other types of traces in Helios, each Lambda trace offers several quick troubleshooting actions. A key action is the ability to replay a specific flow by automatically generating the code and then being able to configure it an use it to reproduce an issue, run it in a different environment, investigate the root cause, and finally verify that it's working properly.
Updated 7 months ago