Lei Wang

OTel Lambda SIG meeting today discussed this topic. Here answer @alolita 's question. ### Why OTel Lambda need CNCF account. From customer's perspective there is not difference between using a...

### Cost estimation To publish public Lambda layer we need a CI/CD workflow to cover integration test, soaking, canary, etc. That needs AWS services Lambda, API Gateway, CloudWatch, Xray and...

### What account does OTel Lambda want OTel Lambda CI/CD will run integration/soaking/canary test by AWS services Lambda, XRay, CloudWatch, CloudFormation, S3, API Gatewa, deploy public Lambda layer in AWS...

Collector extension in opentelemetry-lambda repo currently only has otlp receiver and exporter, and no any processor included. If need components other than them you have to build your custom Collector...

OTel Python SDK otlp exporter has to be packaged in Linux, so `run.sh` use `sam build -u` to make sure the makefile is running in docker linux. https://github.com/open-telemetry/opentelemetry-lambda/blob/main/utils/sam/run.sh#L92

Since now we use TF to build python layer, the Makefile is no longer required.

@vasireddy99 Also refer to issue https://github.com/open-telemetry/opentelemetry-lambda/issues/230. The otel Lambda extension was originally copied from lambda's sample, it contains some meaningless prints for layer user.

Refer design doc, The Collector needs to remove all processors from config to keep one thread only from the receiver to the exporter. In this way, telemetry data is flushed...

Removing processors from Lambda collector extension because we want to make sure force_flush() is blocked until backend returns response to lambda function, the sequence diagram is: force_flush(Lambda runtime, user's Lambda...

Correct something. [This code](https://github.com/open-telemetry/opentelemetry-lambda/blob/main/collector/main.go#L64-L87) does not make sense, remove it or not does not impact anything :) I put it here just because copy from Lambda sample. Lambda Collector extension...