Docs » Instrument serverless functions for Splunk Observability Cloud » Instrument AWS Lambda functions for Splunk Observability Cloud

Instrument AWS Lambda functions for Splunk Observability Cloud 🔗

Use the Splunk OpenTelemetry Lambda layer to automatically instrument AWS Lambda functions to send application metrics and traces to Splunk APM. The layer supports numerous programming languages through integrated wrappers, and includes a metrics extension that collects high-resolution, low-latency metrics every time the function runs.

Select the deployment mode for your AWS Lambda function¶

To instrument your AWS Lambda function using the Splunk OpenTelemetry Lambda layer, select the deployment mode that best adapts to your needs.

Deployment mode

When to use

All-in-one (default)

All components are in a single layer, including the Collector. This is the most comprehensive deployment method and is suited for production environments.

Separate layers

Use separate layers for your language or runtime, Collector, and metric extension. This method reduces performance overhead.

Separate layers with EC2 gateway

Use a layer for your language or runtime and configure the Collector in data forwarding mode in EC2. This is the instrumentation method that uses the least resources, though it requires more configuration.

.NET and Go functions¶

.NET and Go functions require additional instructions:

Collect metrics and logs from AWS CloudWatch¶

Splunk Observability Cloud can also collect AWS Lambda metrics and logs from AWS CloudWatch. See Connect AWS to Splunk Observability Cloud for more information on how to connect Splunk Observability Cloud to your AWS services.

For a walkthrough of tasks related to using AWS cloud services with your infrastructure, see Tutorial: Configure the Splunk Distribution of OpenTelemetry Collector on a Linux host.

This page was last updated on Jul 12, 2024.