Update Lumigo tracer version

Lumigo's tracers constantly improve and unlock new abilities with each version, as detailed in the changelog pages (Python, Node.js, .NET, Go, Java, Python OpenTelemetry distribution, Node.js OpenTelemetry distribution). Some new features may require a newer tracer version, therefore you should periodically ensure you're up to date to get the latest and greatest Lumigo features.

The different ways to apply tracing for Lambda functions include auto-tracing via the Lumigo UI, tagging function in AWS, using Serverless Framework, or manually inserting a tracer dependency in your function. For containerized applications, manual tracing is currently available by adding a dependency.

If you're unsure whether an update will break things, see the section at the end of this document with tips for testing and troubleshooting.

How do I know if I'm currently up to date?

Determine the latest version
The latest version numbers for each language are available on the GitHub release pages: (Python, Node.js, .NET, Go, Java, Python OpenTelemetry distribution, Node.js OpenTelemetry distribution). If you want to be alerted to new releases, sign up for notifications about the relevant repository at GitHub.

Determine the version you're currently using
In the Lumigo interface, hover over the Traced toggle to view the tracer version of the function. If you're not on the latest, consider updating.

18881888

Alternatively, you can leverage the "Add layer" flow in the AWS console to verify the current layer ARN you have in your function. The "Description" section mentions the tracer version (in this example v1.1.209)

18381838

Update your Lumigo tracer version

Follow the steps below to upgrade your Lambda/container tracers according to your tracing appliance method.

When auto tracing via the Lumigo interface:

  • Select the relevant functions
  • Select Untrace
18901890
  • After getting a UI notification that the functions were successfully untraced, select Auto trace (the functions remain selected). When you get the UI notification that the functions are now traced, the latest tracer version is effective!

When auto tracing with AWS tags:

  • Remove or set the lumigo:auto-trace tag to false for all the relevant functions.
  • Wait 15-20 minutes for changes to propagate. (The relevant function will be displayed as not traced in the Lumigo interface)
  • Re-add/set the lumigo:auto-trace tag to true.
  • Wait 15-20 minutes for the changes to propagate. (The relevant function will be displayed as traced in the Lumigo interface)

Note: When using the Lumigo interface or AWS tags, the latest tracer version will be installed, unless a specific version was explicitly set by the user beforehand, under Settings>Tracing menu.

26902690

When auto tracing with Serverless Framework

  • Initiate a function deployment. The latest tracer version will be effective immediately.

When applying manual tracing

  • Initiate a function deployment. The latest tracer version will be effective immediately.
  • Note: if you added the lumigo_tracer package dependency with a specific version set (the dependency looks like lumigo_tracer==), then update the version number to the latest and initiate the deployment.

For containerized applications, when tracing is applied using Lumigo OpenTelemetry Distributions:

  • Rebuild your container image so the dependencies are fetched.
  • Initiate a deployment of your service with the new container image being used.
    Note: if you added the lumigo_opentelemetry package dependency with a specific version set (the dependency looks like lumigo_opentelemetry==), then update the version number to the latest and then apply the steps above.
    Testing & Troubleshooting
    Verifying the upgrade process' success is straightforward, as the invocation views in the Lumigo UI will contain all the relevant information, just like past invocations. However, to ensure tracing is done successfully, you can add the LUMIGO_DEBUG=TRUE environment variable and get extra logging for the tracing activities.
19621962

Although it's very unlikely that upgrading your tracer will cause new errors, record your current "last known good" version so you can roll back to that version if you see new errors after upgrading by leveraging the version pin option under the Settings>Tracing menu.