Using Lumigo OpenTelemetry distributions with other backends

This project contains an AWS Cloud Development Kit (CDK) that shows how to use the Lumigo OpenTelemetry distributions for Javascript and Python with Jaeger.

For example, notice the aws.ecs tags, courtesy of improved Amazon Elastic Container Service (ECS) resource detectors we have contributed upstream (Node.js, Python).

Architecture

How does it work?

The Lumigo OpenTelemetry distributions are built on OpenTelemetry. They come with:

1. no-code installation procedures (just add a depedency and a few env vars, see the Node.js and Python installation procedures)
2. a lot of built-in automation for tracing instrumentations, resource detectors and, of course, exporting to Lumigo
3. additional, fully-automated QA in terms of compatiobility with instrumented packages

All it takes to make the Lumigo OpenTelemetry distributions work with, as in this example, Jaeger, is to add the Jaeger exporter as a dependency, and add it to the TracerProvider objects that the Lumigo OpenTelemetry distributions set up for you, see Node.js example and the Python example.

Requirements

• An AWS account
• AWS CDK v2 installed and configured

Deploy

cdk deploy --all

Part of the output will be something like:

$ cdk deploy --all
...
Outputs:
otelrademojaegerbackend6C6C21C6.ExportsOutputFnGetAttJaegerServiceJaeger45A2A33CDNSName17C5C95F = otelr-Jaege-SLLWJIEKEK2P-1693482168.eu-central-1.elb.amazonaws.com
otelrademojaegerbackend6C6C21C6.JaegerServiceLoadBalancerDNSJaegerA7C8F06D = otelr-Jaege-SLLWJIEKEK2P-1693482168.eu-central-1.elb.amazonaws.com
otelrademojaegerbackend6C6C21C6.JaegerServiceServiceURLJaegerhttpE552ED2E = http://otelr-Jaege-SLLWJIEKEK2P-1693482168.eu-central-1.elb.amazonaws.com  # <-- Jaeger UI url!
...

Then, open you shiny new Jaeger UI with the provided URL.

Removal

Since this is an AWS CDK project, it is as easy as:

cdk destroy --all