The AWS Lambda integration allows you to monitor AWS Lambda—a serverless compute service.

Use the AWS Lambda integration to collect metrics related to your Lambda functions. Then visualize that data in Kibana, create alerts to notify you if something goes wrong, and reference metrics when troubleshooting an issue.

For example, you could use this integration to track throttled lambda functions, alert the relevant project manager, and then increase your account's concurrency limit.

IMPORTANT: Extra AWS charges on AWS API requests will be generated by this integration. Please refer to the AWS integration for more details.

Data streams

The AWS Lambda integration collects one type of data: metrics.

Metrics give you insight into the state of AWS Lambda. Metrics collected by the AWS Lambda integration include the number of times your function code is executed, the amount of time that your function code spends processing an event, the number of invocations that result in a function error, and more. See more details in the Metrics reference.

Requirements

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Before using any AWS integration you will need:

• AWS Credentials to connect with your AWS account.
• AWS Permissions to make sure the user you're using to connect has permission to share the relevant data.

For more details about these requirements, please take a look at the AWS integration documentation.

Setup

Use this integration if you only need to collect data from the AWS Lambda service.

If you want to collect data from two or more AWS services, consider using the AWS integration. When you configure the AWS integration, you can collect data from as many AWS services as you'd like.

For step-by-step instructions on how to set up an integration, see the Getting started guide.

Metrics reference

An example event for lambda looks as following:

{
    "@timestamp": "2022-07-19T22:40:00.000Z",
    "agent": {
        "name": "docker-fleet-agent",
        "id": "2d4b09d0-cdb6-445e-ac3f-6415f87b9864",
        "type": "metricbeat",
        "ephemeral_id": "ed2abfa1-df5e-4c3e-9c2b-143edcc0e111",
        "version": "8.3.2"
    },
    "elastic_agent": {
        "id": "2d4b09d0-cdb6-445e-ac3f-6415f87b9864",
        "version": "8.3.2",
        "snapshot": false
    },
    "cloud": {
        "provider": "aws",
        "region": "eu-central-1",
        "account": {
            "name": "elastic-observability",
            "id": "627286350134"
        }
    },
    "ecs": {
        "version": "8.0.0"
    },
    "service": {
        "type": "aws"
    },
    "data_stream": {
        "namespace": "default",
        "type": "metrics",
        "dataset": "aws.lambda"
    },
    "metricset": {
        "period": 300000,
        "name": "cloudwatch"
    },
    "aws": {
        "lambda": {
            "metrics": {
                "Errors": {
                    "avg": 0
                },
                "ConcurrentExecutions": {
                    "avg": 1
                },
                "Invocations": {
                    "avg": 1
                },
                "UnreservedConcurrentExecutions": {
                    "avg": 1
                },
                "Duration": {
                    "avg": 130.97
                },
                "Throttles": {
                    "avg": 0
                }
            }
        },
        "cloudwatch": {
            "namespace": "AWS/Lambda"
        }
    },
    "event": {
        "duration": 11364562400,
        "agent_id_status": "verified",
        "ingested": "2022-07-26T22:40:40Z",
        "module": "aws",
        "dataset": "aws.lambda"
    }
}

Exported fields

Changelog