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

Is 3rd party exporter in collector-contrib acceptable in Lambda Collector extension?

Open wangzlei opened this issue 4 years ago • 1 comments

Refer discussion in https://github.com/open-telemetry/opentelemetry-lambda/pull/21#discussion_r608305375 Right now Lambda collector extension has only Collect-core exporters, such as otlpgrpcexporter, loggingexporter, etc. Can we bring in popular exporters like awsxrayexporter, datadogexporter?

AWS has maintained a downstream Lambda repo, it publishes public lambda layer by replacing Collector to ADOT Collector for company security concern. That downstream public lambda layer supports lots popular 3rd party exporters in Collect-contrib. If otel-lambda only accept otlp exporter, it means 3rd party companies have to either contribute their exporters to aws-observability or maintaie their downstream repo.

Here we have questions:

  1. can we add 3rd party exporters from Collector-contrib to Lambda Collector extension?
  2. if yes, what criteria an exporter can be involved in?

wangzlei avatar Apr 07 '21 03:04 wangzlei

I think, we might by additional collector layer(s), but we need to be carefully about the coldstart effect of those things during init.

serkan-ozal avatar Sep 02 '24 19:09 serkan-ozal

This issue was marked stale. It will be closed in 30 days without additional activity.

github-actions[bot] avatar Sep 03 '25 03:09 github-actions[bot]

Closed as inactive. Feel free to reopen if this issue is still relevant.

github-actions[bot] avatar Oct 03 '25 03:10 github-actions[bot]