-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
New component: AWS Lambda Telemetry API Receiver #26254
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Sorry for the delay here @driverpt! Pardon my ignorance also, but would the AWS Lambda Extension Layer fit your use case here? Here's another help doc reference. If not, can you describe why not? I don't have much experience in this area so more information would be helpful. |
Hello @crobert-1, this is to be used with Lambda Layer. We have our External Provider api key in a Secret in Secrets Manager. At the moment it's running on ECS w/ Environment Variable injection. We wanted to have the OTEL Collector with the same behavior in Lambda. Since Lambda does not support Secrets like ECS does..... |
Just to confirm, is this a similar request to the issue you've filed against the aws-otel-collector repo? How are they different? I don't have much experience with AWS and its components so I'm looking ways to involve others here. |
It's the same request. |
This should be considered a vendor-specific component, right? I'm going to remove the Feel free to bring this to our weekly collector sig meeting if you don't get a volunteer sponsor otherwise. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
The purpose and use-cases of the new component
To be able to Stream Logs and Telemetry directly from AWS Lambda API
https://docs.aws.amazon.com/lambda/latest/dg/telemetry-api.html
Example configuration for the component
Telemetry data types supported
Traces, Metrics and Logs
Is this a vendor-specific component?
Code Owner(s)
No response
Sponsor (optional)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: