Traces broken when using third party exporter with Lambda about aws-otel-lambda

[wangzlei]

Hi,

The collector inlined in OTel Lambda Python layer is based on aws-otel-collector, so, not all of exporters are supported. Except the strategy reason, we don't involve all of Collector components because we have to control the size of Lambda dependencies due to Lambda limits.

As a workaround, you can build your custom layer, involve the third party exporter you need based on your config. Please see code:
https://github.com/aws-observability/aws-otel-lambda/blob/main/extensions/aoc-extension/cmd/aoc-lambda-extension/main.go#L24
and
https://github.com/aws-observability/aws-otel-collector/blob/main/pkg/lambdacomponents/defaults.go

[katiewest820]

Hey @wangzlei,

Sorry I don't think I explained very well what has been done so far. Yes I have been able to successfully create a custom layer pulling in the New Relic exporter, involving the code you linked.

With these modifications I am able to get the spans generated by actions performed within the function invocation. But what is missing is the upstream span data. In order for this feature to be useful I need to be able to export a complete trace to the third party exporter. This appears to not be possible at the moment?

Is there a way or a future plan to allow users to configure the aws-otel-collector and third party exporter from other AWS services?
My example is API Gateway; I can only export to X-Ray or CloudWatch but in order to collect a complete trace I need to have a way to export those spans to New Relic from somewhere in AWS.

[wangzlei]

Do you mean the spans of API gateway and Lambda service? Those spans are generated by Xray API and sent to xray directly. OpenTelemetry can only handle the span in Lambda container.

[EddieEldridge]

The collector inlined in OTel Lambda Python layer is based on aws-otel-collector

Is this still the case? i.e If I want to find a list of all the available components for the packaged Collector, I should look here ?