-
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
AWS S3 Receiver #24448
Comments
That’s a whole new receiver. Would you like to contribute it? |
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 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 |
Haven't heard back, so closing as inactive. Please reopen if you have further need here. |
But this component is working? |
Please consider coming to a SIG meeting and talk to other contributors. Join the CNCF slack and ask in the #opentelemetry channel. |
Component(s)
No response
Is your feature request related to a problem? Please describe.
I have EMR which store logs on s3, and i need to have ability receive those logs from s3 and send them to elasticsearch
Describe the solution you'd like
Configure s3 receiver which point to bucket with emr logs and stream this data to elasticsearch exporter
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: