Lumigo

For a first Lambda investigation, the documented workflow begins by connecting an AWS account. Lumigo uses an AWS CloudFormation template to create an IAM role; review the generated resources and permissions as part of the team's security approval before applying it. In the Lumigo interface, select Lambda functions and choose Auto-trace, or apply the documented lumigo:auto-trace=true tag. The current serverless guide lists automatic tracing for Python 3.6 and later and Node.js 10.x and later; it directs other runtimes to manual instrumentation. Those version statements come from documentation that appears older, so verify the current runtime guide before relying on them.

When data is available, a transaction view can help follow an execution across services and inspect request context alongside trace information. For example, a team debugging an illustrative checkout flow could use a trace to see which downstream function or API call is associated with the delay, then decide whether to inspect application code, a service dependency, or the request payload. Lumigo describes these views as diagnostic evidence, not an automatic fix.

The pricing page currently lists a free Basic tier with caps on traces, logs, metrics, and retention, alongside Standard, Plus, and Custom plans. It also advertises a 14-day trial without payment details and says a trial account moves to the free tier afterward. Check the billing toggle and plan limits when comparing the displayed paid amounts; exact overage and customer-specific terms were not established here.

There is a product-identity caveat: Lumigo's current site carries a notice that it is joining Dash0, and Dash0's February 4, 2026 announcement says Lumigo capabilities will be integrated over time. The Lumigo product and pricing pages remained available during this research, so this record describes the separately documented Lumigo service without assuming how or when it will be consolidated. No account or instrumentation was created.