Rework FaaS semantic conventions. #1781
Conversation
Oberon00
added
area:semantic-conventions
| Depending on the cloud provider, use: | ||
|
|
||
| * **AWS Lambda:** The function [ARN](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html). | ||
| Take care not to use the "invoked ARN" directly but replace any |
There was a problem hiding this comment.
Do you know if this is possible?
There was a problem hiding this comment.
The string replacement or that "the same runtime instance may be invokable with multiple different aliases"? Yes, I verified both. You can easily produce that scenario with the Lambda console UI by creating two different aliases for $LATEST and then you can test both and you will see that the logs end up in the same logstream without restart.
You can even test it without creating an extra alias. E.g. using aws lambda invoke --function-name 'arn:aws:lambda:us-east-1:12345:function:myfunction:$LATEST will end up with a different invoked ARN than just aws lambda invoke --function-name 'arn:aws:lambda:us-east-1:12345:function:myfunction, but the same invoked version & log stream.
|
@mateuszrzeszutek Please review whenever you have cycles ;) |
|
@Oberon00 Please update your branch so we can merge this 👍 |
Fixes #1280 (through introduction of aws.lambda.invoked_arn span attribute, @mateuszrzeszutek please check if that is OK).
Addresses #1778.
Changes
aws.lambda.invoked_arnand clarify that alias must be stripped fromfaas.idresource attribute for AWS Lambda.CC @skonto