Change transaction.name for API Gateway-triggered Lambda functions: To be consistent with other HTTP-based instrumentations include the low-cardinality resourcePath into the name.
Respect setting for use_path_as_transaction_name: If use_path_as_transaction_name is enabled use the full HTTP path for the transaction.name in API Gateway-triggered Lambda functions.
Respect service_name and service_version agent config options: If service_name and/or service_version are explicitly configured use the configured values instead of the derived ones.
Use the full domain name of the API Gateway as service.origin.name
Replaced service.id metadata field with new transaction-level field faas.id: To being able to capture different Lambda function ARN values (semantically correct) under one APM service umbrella (for the scenario of consolidating multiple lambda functions in one APM service).
Spec PR: https://github.com/elastic/apm/pull/579
Changes
transaction.namefor API Gateway-triggered Lambda functions: To be consistent with other HTTP-based instrumentations include the low-cardinality resourcePath into the name.use_path_as_transaction_name: Ifuse_path_as_transaction_nameis enabled use the full HTTP path for thetransaction.namein API Gateway-triggered Lambda functions.service_nameandservice_versionagent config options: Ifservice_nameand/orservice_versionare explicitly configured use the configured values instead of the derived ones.service.origin.nameservice.idmetadata field with new transaction-level fieldfaas.id: To being able to capture different Lambda function ARN values (semantically correct) under one APM service umbrella (for the scenario of consolidating multiple lambda functions in one APM service).Status
Issue tracking
- [x] https://github.com/elastic/apm-agent-java/issues/2394 - [x] https://github.com/elastic/apm-agent-nodejs/issues/2531 - [x] https://github.com/elastic/apm-agent-python/issues/1446