Lambda- successive invocations reusing first invocation's facade segment

[Dave-McCraw]

Successive invocations of a lambda are adding to the trace of the initial invocation. I presume I've got this set up incorrectly but I'm struggling to identify what it is.

The first invocation trace looks like:

A later one looks like this:

Simplified code:

const AWSXRay = require("aws-xray-sdk");
const AWS = AWSXRay.captureAWS(require("aws-sdk"));
const AWS_EXECUTION_ENV = process.env.AWS_EXECUTION_ENV;

async function processLocation(event) {
  AWSXRay.setContextMissingStrategy(() => {});
  xrayEnabled = !!AWS_EXECUTION_ENV;

  if (xrayEnabled) {
    let facadeSegment = AWSXRay.getSegment();
    console.log("Starting segment is called: " + facadeSegment.name); 
    let segment = facadeSegment.addNewSubsegment("Root");
    AWSXRay.setSegment(segment);
    segment.addMetadata("event data", JSON.stringify(event));
  }

The log statement outputs:

Any pointers?

Later in the lambda I call AWSXRay.setSegment(subSegment); before making parallel HTTP calls otherwise I found the auto-instrumented segments using captureHTTPsGlobal wouldn't attach to the correct parent segments. It's around here that it smells bad to me.

[Dave-McCraw]

OK, so I can "fix" this by removing all my calls to AWSXRay.setSegment(), now each invocation has its own segments again.

Unfortunately it loses the association between instrumented outbound calls and their parent segments.

What's the correct way to get this:

Without using AWSXRay.setSegment()? When I comment it out, I get this instead:

where the invoked lambda or captureHTTPsGlobal() calls just pile up at the bottom randomly.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in next 7 days. Thank you for your contributions.

[willarmiros]

Sorry for missing this @Dave-McCraw. You shouldn't need to use setSegment as you've identified.

Unfortunately it loses the association between instrumented outbound calls and their parent segments.

Which subsegments in your screenshots represent the outbound HTTP requests you mentioned? Are they being attached to entirely different invocation segments, or just in the wrong place in the hierarchy, but still eventually parented to the correct segment?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in next 7 days. Thank you for your contributions.