AWS Lambda
Metrics
Deploy this integration to send your Amazon Lambda metrics to Logz.io.
This integration creates a Kinesis Data Firehose delivery stream that links to your Amazon Lambda metrics stream and then sends the metrics to your Logz.io account. It also creates a Lambda function that adds AWS namespaces to the metric stream, and a Lambda function that collects and ships the resources' tags.
Log in to your Logz.io account and navigate to the current instructions page inside the Logz.io app. Install the pre-built dashboard to enhance the observability of your metrics.
To view the metrics on the main dashboard, log in to your Logz.io Metrics account, and open the Logz.io Metrics tab.
Before you begin, you'll need:
- An active account with Logz.io
Configure AWS to forward metrics to Logz.io
Create Stack in the relevant region
To deploy this project, click the button that matches the region you wish to deploy your Stack to:
| Region | Deployment |
|---|---|
us-east-1 |  |
us-east-2 | |
us-west-1 | |
us-west-2 | |
eu-central-1 | |
eu-north-1 | |
eu-west-1 | |
eu-west-2 | |
eu-west-3 | |
sa-east-1 | |
ap-northeast-1 | |
ap-northeast-2 | |
ap-northeast-3 | |
ap-south-1 | |
ap-southeast-1 | |
ap-southeast-2 | |
ca-central-1 | |
Specify stack details
Specify the stack details as per the table below, check the checkboxes and select Create stack.
| Parameter | Description | Required/Default |
|---|---|---|
logzioListener | The Logz.io listener URL for your region. (For more details, see the regions page. For example - https://listener.logz.io:8053 | Required |
logzioToken | Your Logz.io metrics shipping token. | Required |
awsNamespaces | Comma-separated list of the AWS namespaces you want to monitor. See this list of namespaces. If you want to automatically add all namespaces, use value all-namespaces. | Required |
logzioDestination | Your Logz.io destination URL. | Required |
httpEndpointDestinationIntervalInSeconds | The length of time, in seconds, that Kinesis Data Firehose buffers incoming data before delivering it to the destination. | 60 |
httpEndpointDestinationSizeInMBs | The size of the buffer, in MBs, that Kinesis Data Firehose uses for incoming data before delivering it to the destination. | 5 |
Check Logz.io for your metrics
Give your data some time to get from your system to ours, then log in to your Logz.io Metrics account, and open the Logz.io Metrics tab.
Log in to your Logz.io account and navigate to the current instructions page inside the Logz.io app. Install the pre-built dashboard to enhance the observability of your metrics.
To view the metrics on the main dashboard, log in to your Logz.io Metrics account, and open the Logz.io Metrics tab.
Traces
Deploy this integration to auto-instrument your Node.js application running on AWS Lambda and send the traces to your Logz.io account. This is done by adding a dedicated layer for OpenTelemetry collector, a dedicated layer for Node.js auto-instrumentation and configuring environment variables of these layers. This integration will require no change to your application code.
This integration only works for the following AWS regions: us-east-1, us-east-2, us-west-1, us-west-2,ap-south-1, ap-northeast-3, ap-northeast-2, ap-southeast-1, ap-southeast-2, ap-northeast-1, eu-central-1, eu-west-1, eu-west-2, eu-west-3, eu-north-1, sa-east-1, ca-central-1.
Before you begin, you'll need:
- AWS CLI
- Configured AWS credentials
- A Lambda function with a Node.js application that is not yet instrumented.
Adding environmental variables using the AWS CLI commands below, will overwrite all existing variables for your Lambda function.
This integration uses OpenTelemetry Collector Contrib, not the OpenTelemetry Collector Core.
Add the OpenTelemetry collector layer to your Lambda function
This layer contains the OpenTelemetry collector that will capture data from your application.
aws lambda update-function-configuration --function-name <<YOUR-LAMBDA_FUNCTION_NAME>> --layers arn:aws:lambda:<<YOUR-AWS-REGION>>:486140753397:layer:logzio-opentelemetry-collector-layer:<<LAYER_VERSION>>
Replace <<YOUR-LAMBDA_FUNCTION_NAME>> with the name of your Lambda function running the Node.js application.
Replace <<YOUR-AWS-REGION>> with the code of your AWS regions, e.g. us-east-1.
Replace <<LAYER_VERSION>> with the latest stable version for your region.
| Region | logzio-opentelemetry-collector-layer |
|---|---|
| us-east-1 | 14 |
| us-east-2 | 3 |
| us-west-1 | 2 |
| us-west-2 | 2 |
| eu-north-1 | 2 |
| eu-west-1 | 3 |
| eu-west-2 | 3 |
| eu-west-3 | 2 |
| ca-central-1 | 3 |
| ap-northeast-1 | 3 |
| ap-northeast-2 | 3 |
| ap-northeast-3 | 2 |
| ap-south-1 | 2 |
| ap-southeast-1 | 2 |
| ap-southeast-2 | 2 |
| sa-east-1 | 2 |
Create a configuration file for the OpenTelemetry collector
By default, the OpenTelemetry collector layer exports data to the Lambda console. To customize the collector configuration, you need to add a collector.yaml to your function and specifiy its location via the OPENTELEMETRY_COLLECTOR_CONFIG_FILE environment variable.
The collector.yaml file will have the following configuration:
receivers:
otlp:
protocols:
grpc:
endpoint: "0.0.0.0:4317"
http:
endpoint: "0.0.0.0:4318"
exporters:
logzio/traces:
account_token: "<<TRACING-SHIPPING-TOKEN>>"
region: "<<LOGZIO_ACCOUNT_REGION_CODE>>"
service:
pipelines:
traces:
receivers: [otlp]
exporters: [logzio/traces]
Replace <<TRACING-SHIPPING-TOKEN>> with the token of the account you want to ship to.
Replace <LOGZIO_ACCOUNT_REGION_CODE> with the applicable region code.
The tail_sampling defines the decision to sample a trace after the completion of all the spans in a request. By default, this configuration collects all traces that have a span that was completed with an error, all traces that are slower than 1000 ms, and 10% of the rest of the traces.
You can add more policy configurations to the processor. For more on this, refer to OpenTelemetry Documentation.
The configurable parameters in the Logz.io default configuration are:
| Parameter | Description | Default |
|---|---|---|
| threshold_ms | Threshold for the spand latency - all traces slower than the threshold value will be filtered in. | 1000 |
| sampling_percentage | Sampling percentage for the probabilistic policy. | 10 |
Direct the OpenTelemetry collector to the configuration file
Add OPENTELEMETRY_COLLECTOR_CONFIG_FILE variable to direct the OpenTelemetry collector to the configuration file:
aws lambda update-function-configuration --function-name <<YOUR-LAMBDA_FUNCTION_NAME>> --environment Variables={OPENTELEMETRY_COLLECTOR_CONFIG_FILE=/var/task/collector.yaml}
Replace <<YOUR-LAMBDA_FUNCTION_NAME>> with the name of your Lambda function running the Node.js application.
Activate tracing for your Lambda function
aws lambda update-function-configuration --function-name <<YOUR-LAMBDA_FUNCTION_NAME>> --tracing-config Mode=Active
Replace <<YOUR-LAMBDA_FUNCTION_NAME>> with the name of your Lambda function running the Node.js application.
Add the OpenTelemetry Node.js wrapper layer to your Lambda function
The OpenTelemetry Node.js wrapper layer automatically instruments the Node.js application in your Lambda function.
aws lambda update-function-configuration --function-name <<YOUR-LAMBDA_FUNCTION_NAME>> --layers arn:aws:lambda:<<YOUR-AWS-REGION>>:486140753397:layer:logzio-opentelemetry-nodejs-wrapper:<<LAYER_VERSION>>
Replace <<YOUR-LAMBDA_FUNCTION_NAME>> with the name of your Lambda function running the Node.js application.
Replace <<YOUR-AWS-REGION>> with the code of your AWS regions, e.g. us-east-1.
Replace <<LAYER_VERSION>> with the latest stable version for your region.
| Region | logzio-opentelemetry-nodejs-wrapper |
|---|---|
| us-east-1 | 11 |
| us-east-2 | 3 |
| us-west-1 | 2 |
| us-west-2 | 2 |
| eu-north-1 | 2 |
| eu-west-1 | 3 |
| eu-west-2 | 3 |
| eu-west-3 | 2 |
| ca-central-1 | 3 |
| ap-northeast-1 | 3 |
| ap-northeast-2 | 3 |
| ap-northeast-3 | 2 |
| ap-south-1 | 2 |
| ap-southeast-1 | 2 |
| ap-southeast-2 | 2 |
| sa-east-1 | 2 |
Add environment variable for the wrapper
Add the AWS_LAMBDA_EXEC_WRAPPER environment variable to point to the otel-handler executable:
aws lambda update-function-configuration --function-name <<YOUR-LAMBDA_FUNCTION_NAME>> --environment Variables={AWS_LAMBDA_EXEC_WRAPPER=/opt/otel-handler}
Replace <<YOUR-LAMBDA_FUNCTION_NAME>> with the name of your Lambda function running the Node.js application.
For a much easier and more efficient way to collect and send metrics, consider using the Logz.io telemetry collector.