Containerized applications

Documentation to get you started monitoring containerized applications with Lumigo and OpenTelemetry.

Containers are integrated in transactions alongside Lambda functions, DynamoDB, SQS, third-party services and everything else Lumigo supports.


A transaction shown in Lumigo that spans an ECS task running a FastAPI application, several Lambda functions, DynamoDB, SNS and Twilio


You can try it today, for free!

This screenshot is taken from Lumigo's Sandbox, feel free to go try it for yourself!

Lumigo's support for containerized applications is based on OpenTelemetry and it comes in two flavors:

  1. Lumigo OpenTelemetry Distributions
  2. Support for "vanilla" OpenTelemetry

Lumigo OpenTelemetry Distributions

The Lumigo's own tracers for containerized applications are distributions of OpenTelemetry, available for the following programming languages:

Lumigo's distributions of OpenTelemetry are based on upstream, selected OpenTelemetry packages, and have additional capabilities:

  • No-code injection: The distributions can be added to your applications without code changes to the applications themselves; the distribution is an additional dependency you add to your application at build time, and are activated and configured exclusively via environment variables.

  • Automated regression testing: All the automatic instrumentation included in Lumigo distributions of OpenTelemetry are rigorously, automatically tested for compatibility with all available versions of the packages they instrument. As new versions of an instrumented package are released, we automatically check for its compatibility and add it to the support matrix.


Wishing for a Lumigo Distribution of OpenTelemetry for a different programming language?

If you would like the ease of use of the Lumigo Distributions of OpenTelemetry for a programming language we do not support yet, please let us know!

OpenTelemetry to monitor containerized applications

Lumigo supports "vanilla" OpenTelemetry, that is, the OpenTelemetry SDKs and implementations provided by the community, as documented by the OpenTelemetry Support section.

What should you use?

  1. If your applications are not already instrumented with OpenTelemetry and there is a Lumigo OpenTelemetry Distribution for the programming languages the applications are built with, go ahead and use the Lumigo OpenTelemetry Distribution: they are super easy to adopt and work out of the box with Lumigo.
  2. If your applications are not already instrumented with OpenTelemetry but there is no Lumigo OpenTelemetry Distribution yet for the programming languages the applications are built with, then use the community OSS OpenTelemetry that fits you best; the Other OpenTelemetry implementations section provides pointers to get you started.
  3. If your applications are already instrumented with OpenTelemetry, as it happens with increasingly more third-party components every day, then use the instrumentation you already have.
    The OpenTelemetry Support provides a lot of sample configurations for many OpenTelemetry SDKs out there.


Questions about adding OpenTelemetry to your applications?

If you are having issues connecting an application instrumented with OpenTelemetry with Lumigo, please contact our support.