Forward trace context to AWS Batch job

[Kralizek]

Hi,

In my application I have a step where an API call eventually submits a job to Batch. The application performing the task will then call other services and consume other AWS services.

What's the best course of action for the calling application to forward the trace context to the application being used by Batch to perform the job?

I guess I can pass the trace-id as a parameter to the application, but is there a way to explicitly set up the recorder to append segments to that trace?

[lupengamzn]

Hi @Kralizek,

Does the API call an Asp.Net(Core) application? If so, you can follow the implementations as usual and X-Ray's Asp.Net handler will automatically fetch and parse the upstream trace id for you. If not, you may have to manually parse the trace id and pass it to the segment that you create for this application.

[Kralizek]

Hi @lupengamzn

The receiving application is a console application that will be executed by Batch for each item so I'm left to parse the trace id and pass it as an environment variable in the container overrides part of the submit job request.

Is there a convenient way to access the current trace id? I was hoping for something in the TraceContext like AWSXRayRecorder.Instance.TraceContext.TraceId but couldn't find anything.

[srprash]

Hi @Kralizek

Is there a convenient way to access the current trace id?

You can use AWSXRayRecorder.Instance.GetEntity().TraceId for that.
Ref Doc: https://docs.aws.amazon.com/xray-sdk-for-dotnetcore/latest/reference/html/P_Amazon_XRay_Recorder_Core_Internal_Entities_Entity_TraceId.htm