Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support build Lambda Collector extension layer on demand #100

Closed
wangzlei opened this issue Jun 4, 2021 · 3 comments
Closed

Support build Lambda Collector extension layer on demand #100

wangzlei opened this issue Jun 4, 2021 · 3 comments
Labels

Comments

@wangzlei
Copy link
Contributor

wangzlei commented Jun 4, 2021

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
@dglozano
Copy link

dglozano commented May 4, 2022

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

Copy link

github-actions bot commented Sep 8, 2024

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

@github-actions github-actions bot added the Stale label Sep 8, 2024
Copy link

github-actions bot commented Oct 8, 2024

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants