opentelemetry-lambda icon indicating copy to clipboard operation
opentelemetry-lambda copied to clipboard

Support build Lambda Collector extension layer on demand

Open wangzlei opened this issue 3 years ago • 1 comments

At the moment Lambda Collector extension layer contains very limit components due to the the reason described here.

Adding more collector components into code is cautious because we don't want to inflate the binary size, and also for neutrality we suggest Vendor maintains its downstream repo. For example aws-otel-lambda contains AWS XRay exporter and EMF exporter.

Ideally, we want to provide a mechanism to let user easily build a custom collector extension layer based on his demand. Here give an option by using opentelemetry-collector-builder, so user can dynamically build and publish custom lambda layer to his individul AWS account:

  1. download this repo
  2. go to collector folder
  3. create his Collector config custom.yml under folder collector
  4. run make publishpublish-layer

wangzlei avatar Jun 04 '21 01:06 wangzlei

Is there any time estimate on this or possible workaround until it's resolved? We would love to use open telemetry in our lambdas and send traces to Datadog, but the only way to do that it seems to be by using the datadog exporter in the collector, which is not included in the layer version of it

dglozano avatar May 04 '22 08:05 dglozano