Skip to content

AWS Lambda detector: incorrect faas.max_memory value #7591

@sahidvelji

Description

@sahidvelji

Description

According to the faas semconv, faas.max_memory should be reported in bytes, not in MB.

The semconv explicitly states that

On AWS Lambda, the environment variable AWS_LAMBDA_FUNCTION_MEMORY_SIZE provides this information (which must be multiplied by 1,048,576).

https://opentelemetry.io/docs/specs/semconv/resource/faas/#:~:text=On%20AWS%20Lambda%2C%20the%20environment%20variable%20AWS_LAMBDA_FUNCTION_MEMORY_SIZE%20provides%20this%20information%20(which%20must%20be%20multiplied%20by%201%2C048%2C576).

Supporting documentation:

AWS_LAMBDA_FUNCTION_MEMORY_SIZE – The amount of memory available to the function in MB.

https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#:~:text=AWS_LAMBDA_FUNCTION_MEMORY_SIZE%20%E2%80%93%20The%20amount%20of%20memory%20available%20to%20the%20function%20in%20MB.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

Status
Closed

Relationships

None yet

Development

No branches or pull requests

Issue actions