Some instrumentations (as Baselime: https://baselime.io/docs/sending-data/otel/) inject their instrumentation via NODE_OPTIONS=--require... instead of AWS_LAMBDA_EXEC_WRAPPER
We respect all other eventually set NODE_OPTIONS, so in case of Baselime it'll result with setting as --require <baseline module> --require <console module>.
As I tested Node.js respects input for all --require calls, and loads them in provided order, so that is not breaking for Baselime. Yet to ensure most correct instrumentation outcome it'll be better if our instrumentation is loaded first. This PR ensures that
Some instrumentations (as Baselime: https://baselime.io/docs/sending-data/otel/) inject their instrumentation via
NODE_OPTIONS=--require...instead ofAWS_LAMBDA_EXEC_WRAPPEROur instrumentation applies same method yet it's done via module pointed in
AWS_LAMBDA_EXEC_WRAPPERenv variable: https://github.com/serverless/console/blob/795bb111be87a6aa728a9b947f7b8de3c09f5581/node/packages/aws-lambda-sdk/internal-extension/exec-wrapper.sh#L3We respect all other eventually set
NODE_OPTIONS, so in case of Baselime it'll result with setting as--require <baseline module> --require <console module>.As I tested Node.js respects input for all
--requirecalls, and loads them in provided order, so that is not breaking for Baselime. Yet to ensure most correct instrumentation outcome it'll be better if our instrumentation is loaded first. This PR ensures that