Lumigo incident
Issues with autotrace for Node.js 18 functions defined as modules
Lumigo experienced a minor incident on December 19, 2022 affecting Tracer, lasting 1d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Dec 19, 2022, 05:24 PM UTC
We have seen a spike of issues related to auto-tracing Lambda functions using the Node.js 18 runtime. We believe this is related to the fact that we have not yet implemented support for .mjs files, and when auto trace is applied, the Lumigo Node.js tracer may fail to find the original handler to dispatch function calls to. We are disabling the support for auto-tracing Node.js 18 on new functions until the issue is resolved. We are very sorry for the inconvenience.
- identified Dec 19, 2022, 10:04 PM UTC
We are working on it to restore the full functionality
- identified Dec 20, 2022, 11:25 AM UTC
Update about the Lambda Node + mjs (a.k.a “ES modules” / “ESM” / “EcmaScript Modules”) situation: we think we have a fix for the Node.js tracer that would restore auto-trace for all known use cases (including .cjs that was so far not supported). We are going to run very stringent tests for it. ETE by EoD, assuming we do not find further issues.
- monitoring Dec 20, 2022, 03:08 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Dec 20, 2022, 03:08 PM UTC
We are continuing to monitor for any further issues.
- resolved Dec 20, 2022, 06:47 PM UTC
This incident has been resolved.