Monitor AWS Lambda Metrics with SigNoz

One-Click Integration

The One-Click AWS Integration automatically configures the collection of Lambda metrics and logs. It uses CloudWatch Metric Streams to stream data to SigNoz.

Setup

See the detailed guide: AWS Lambda Integration

This covers:

1. Connecting your AWS Account.
2. Enabling Lambda metric collection.
3. Accessing pre-built dashboards for Invocations, Errors, Duration, and more.

Manual Setup (CloudWatch Exporter)

To collect AWS Lambda metrics manually, you can use the Prometheus CloudWatch Exporter. This tool scrapes metrics from AWS CloudWatch and exposes them in Prometheus format, which the OpenTelemetry Collector can then scrape and forward to SigNoz.

Prerequisites

Before proceeding, ensure you have:

• OpenTelemetry Collector installed and configured. See Get Started with OTel Collector.
• Java 11 or higher installed on the host machine (for JAR-based setup), or Docker (for container-based setup).
• AWS credentials configured via environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY), IAM role, or ~/.aws/credentials.
• IAM permissions for the credentials:
  • cloudwatch:ListMetrics
  • cloudwatch:GetMetricStatistics

Where to Run the CloudWatch Exporter

The CloudWatch Exporter should run on a machine that:

1. Has network access to AWS CloudWatch APIs.
2. Has AWS credentials configured.
3. Is network-accessible from your OpenTelemetry Collector.

For SigNoz Cloud users, run the exporter on any EC2 instance, VM, or container with AWS credentials. The OTel Collector on the same host will forward metrics to SigNoz Cloud.

For Self-Hosted users, run the exporter on the same host as your OTel Collector, or ensure network connectivity between them.

Step 1: Create Configuration File

Create a file named lambda-metrics.yaml with the following configuration. This defines which metrics to fetch from the AWS/Lambda namespace.

region: <aws-region>
metrics:
  - aws_namespace: AWS/Lambda
    aws_metric_name: Invocations
    aws_dimensions: [FunctionName]
    aws_statistics: [Sum]

  - aws_namespace: AWS/Lambda
    aws_metric_name: Errors
    aws_dimensions: [FunctionName]
    aws_statistics: [Sum]

  - aws_namespace: AWS/Lambda
    aws_metric_name: Duration
    aws_dimensions: [FunctionName]
    aws_statistics: [Average, Maximum]
    aws_extended_statistics: [p99]

  - aws_namespace: AWS/Lambda
    aws_metric_name: Throttles
    aws_dimensions: [FunctionName]
    aws_statistics: [Sum]

  - aws_namespace: AWS/Lambda
    aws_metric_name: ConcurrentExecutions
    aws_dimensions: [FunctionName]
    aws_statistics: [Maximum]

Verify these values:

• <aws-region>: Your AWS region where Lambda functions are deployed (e.g., us-east-1, eu-west-1, ap-south-1).

See example configurations for more service templates.

Step 2: Download and Run the Exporter

curl -LO https://repo1.maven.org/maven2/io/prometheus/cloudwatch/cloudwatch_exporter/0.16.0/cloudwatch_exporter-0.16.0-jar-with-dependencies.jar

java -jar cloudwatch_exporter-0.16.0-jar-with-dependencies.jar 9106 lambda-metrics.yaml

docker run -d \
  --name cloudwatch-exporter \
  -p 9106:9106 \
  -v $(pwd)/lambda-metrics.yaml:/config/config.yml \
  -e AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID \
  -e AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY \
  prom/cloudwatch-exporter

Verify the exporter is running by checking the metrics endpoint:

curl http://localhost:9106/metrics | grep aws_lambda

You should see metrics like aws_lambda_invocations_sum, aws_lambda_errors_sum, etc.

Step 3: Configure OpenTelemetry Collector

Add the following prometheus receiver to your existing otel-collector-config.yaml to scrape the CloudWatch Exporter:

receivers:
  prometheus:
    config:
      scrape_configs:
        - job_name: 'lambda-cloudwatch'
          scrape_interval: 60s
          static_configs:
            - targets: ['<exporter-host>:9106']

Verify these values:

• <exporter-host>: The hostname or IP where the CloudWatch Exporter is running. Use localhost if running on the same machine.

Enable the prometheus receiver in your metrics pipeline by updating the service section:

service:
  pipelines:
    metrics:
      receivers: [otlp, prometheus]
      processors: [batch]
      exporters: [otlp]

Restart your OpenTelemetry Collector to apply the changes.

Validate

To confirm that Lambda metrics are flowing to SigNoz:

1. Navigate to Dashboards → New Dashboard → New Panel in SigNoz.
2. In the query builder, search for metrics starting with aws_lambda_ (e.g., aws_lambda_invocations_sum).
3. Verify that metrics appear with function_name labels matching your Lambda functions.

If you see metrics with labels like function_name, your setup is working correctly.