AWS update FAQ page
Note
AWS is rolling out an update that may cause transactions in Lumigo to appear incorrectly when using old versions of the Lumigo Node.js tracers.
To keep Transactions in Lumigo correct and accurate, please update the Lumigo tracer on your Node.js Lambda functions to version 1.101.2 or above.
To update your Node.js tracer version to version 1.101.2 or above you can follow the documentation, or contact us.
Does this AWS update affect my Lambda functions in any way?
No. Your functions will be unaffected and continue to run as before. However, transactions will not appear correctly in Lumigo.
Does this AWS update affect tracers of runtimes other than Node?
No it doesn’t. Only Node.js Lambda tracers need to be updated.
To what version should I update my tracer?
To the latest version (1.101.2 or above).
How can I update my tracer?
To update your Node.js tracer you can follow the documentation, or contact us.
I use auto-tracing, do I also need to update?
Yes. All Node.js Lambdas functions with the Lumigo tracer need to be updated. Since you’re using auto-tracing, you can easily do it right from your Lumigo UI.
Where can I see the current tracer version for a particular function?
To view the tracer version for a particular function, go to Functions, and hover over the Traced toggle to view the tracer version.
I updated the function, but Lumigo still shows an older tracer version. Why?
Lumigo KNOWS that a function has been updated to a new tracer version only when it receives a trace with the new tracer. This is the case even if a Lumigo layer is configured on the function, because your function might have a different
@lumigo/tracerpackage in the dependencies innode_modules.
Verifying the tracer version and LUMIGO_SWITCH_OFF
If your function has the
LUMIGO_SWITCH_OFF=trueenvironment variable or uses theswitchOffoption of thelumigo.tracefunction (in case of manual tracing), no trace data will be sent to Lumigo, so Lumigo cannot verify that the tracer has actually been updated.
Updated 6 months ago