AWS Lambda
The following cost calculation tags are required for traces originating from AWS Lambda functions:
| Attribute Name | Example Value | Allowed Values |
|---|---|---|
| aws.lambda.arn | arn:aws:lambda:us-east-1:123456789012:function:my_examle_function | Any valid arn |
| aws.lambda.architecture | x86_64 | arm64, x86_64 |
| aws.lambda.memory_size | 2048 | Any valid Lambda memory limit |
| aws.region | us-east-1 | Any valid Lambda region |
Required for CUR Cost Finalization
Costs calculated from the tags above are provisional — estimated from list prices. When you connect your AWS Cost and Usage Report (CUR), Beakpoint Insights replaces provisional costs with your actual billed costs by matching spans to CUR line items. That matching requires one additional tag:
| Attribute Name | Example Value | Allowed Values |
|---|---|---|
cloud.resource_id | arn:aws:lambda:us-east-1:123456789012:function:my_example_function | The full function ARN (the same value as aws.lambda.arn) |
Must be a resource attribute
cloud.resource_id should be set as an OpenTelemetry resource attribute. Spans sent directly via OTLP will not match your CUR data if the tag only appears at the span level, and their costs will remain provisional indefinitely. (Traces imported from AWS X-Ray have span-level values promoted automatically, but do not rely on this.)