Handling Traces through a serverless framework API without caller control

Data Prepper
4

@mentzerk Thanks for sharing. For 1, we will need to do some further investigation on the trace structure produced by the lambda instrumentation library and will reach back for further info if necessary. Just to follow-up and clarify on

We can only get traces into the trace analytics plugin if we explicitly set the ROOT_CONTEXT in a new span within the Lambda

  1. By get traces into the trace analytics do you mean that traceGroup and traceGroupFields will not be empty if you explicitly set the ROOT_CONTEXT? I expect the spans will still be exported successfully to the opensearch backend anyway. The difference is whether traceGroup is populated successfully.

  2. Would you mind give an example on how explicitly setting ROOT_CONTEXT manifest itself in a new span?

For 2, would you mind share any sample spans that all belong to a particular traceId? In particular, we would like to know what the root span in Service A look like in its key-value’s, which might help us establish new criteria.