Update Lumigo tracer version

Lumigo's tracers constantly improve and unlock new abilities with each version. 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.

There are several ways to update the Lumigo's tracers:

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.

❗️

Note

AWS is rolling out an update that may collide with old versions of Lumigo Node.js tracers.

A Node.js tracer version that has not been updated might disrupt your AWS environment as well as your ability to use the Lumigo platform.

To update your Node.js tracer to version 1.80.1 or later you can follow the documentation, or contact us.

If you can't find the answer you are looking for? Read these FAQ or contact us.

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

To view functions that reuiqre updating their tracer, go to the Functions page. Functions need to updated will be marked in red.

2820

To determine the tracer version you're currently using go to the Functions, and hover over the Traced toggle to view the tracer version of the function.

2686

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)

1838

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.

Update Lumigo tracer version installed from the Lumigo UI

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

When auto tracing via the Lumigo interface:

  • Login to the platform. A dialog page will be opened, with the list of Node.js functions need updating.
  • Click on the "Update functions" button
  • The functions will be auto-updated. This can take a few minutes.
2182

📘

Note

Only functions that have been auto-trace can be updated via the UI. If there are additional functions that have been manually traced, please follow the instructions below.

Update Lumigo tracer version installed via AWS tags

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.

2690

Update Lumigo tracer version installed via Serverless Framework

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.

Update Lumigo tracer version installed via Lumigo CDK Constructs

When the Lumigo CDK Constructs, you need to:

  • Update the version of the @lumigo/cdk-constructs-v2 package in your CDK repository, as we release a new version of @lumigo/cdk-constructs-v2 every time a Lambda tracer is updated, using the latest version by default
  • Trigger an update of your CDK application using your cdk deploy workflow.

Update Lumigo tracer version installed in containers

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.
1962

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.