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

S3 Exporter in ADOT #1615

Open
anish-aws opened this issue Nov 8, 2022 · 17 comments
Open

S3 Exporter in ADOT #1615

anish-aws opened this issue Nov 8, 2022 · 17 comments
Assignees
Labels
ADOT collector ADOT Collector related issues exporter Exporter related feature-request Feature request stale

Comments

@anish-aws
Copy link

anish-aws commented Nov 8, 2022

Is your feature request related to a problem? Please describe.
I am working with a team that wants to export application traces into long term storage. The team has needs to perform custom analysis (things not provided by services like DataDog) over the long term and also analyse traces data in conjunction with other data sets from various sources. They want the ability to move the trace data into cheap and durable storage like S3 and use tools like Athena, EMR, SageMaker, etc to perform analysis.

Describe the solution you'd like
The solution requested would be the ability to configure an S3 exporter, similiar to other exporters like X-Ray exporter or Prometheus Exporter. The exporter would take in configuration like the bucket name, path, etc and the ADOT collector will ship trace information into the S3 bucket. From there on downstream systems can consume it as they like. Current use case for the team is to export traces, but future use cases exist for similiar functionality with logs and metrics

Describe alternatives you've considered
Other options like Kinesis Exporter and X-Ray exporter was considered. this adds additional step in the data movement to downstream systems and cost. This also requires a substantial engineering effort to standup the solution and maintain it. Analysis inside current services like DataDog or Jaeger is limited as performing long term query analysis with multi source data sets is either technically impossible (such as exporting data from DataDog) or cost prohibitive.
Open-source alternatives like Parquet exporter are currently in beta and would also require the engineering time to build a solution to move data from the container system into S3. The expectation is for the S3 exporter and the collector to do this activity, if built

@mhausenblas
Copy link
Member

Thanks @anish-aws, we will have a look into it and update this feature request within the next couple of days.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Jan 15, 2023
@anish-aws
Copy link
Author

Commenting for bot. but also, any update on this request?

@mhausenblas
Copy link
Member

@anish-aws we're in the review process, gathering input. No confirmed ECD yet.

@mhausenblas mhausenblas added exporter Exporter related ADOT collector ADOT Collector related issues and removed stale labels Jan 16, 2023
@anish-aws
Copy link
Author

Linking open issue from Upstream that seems to have a sponsor as of last week
open-telemetry/opentelemetry-collector-contrib#2835

@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@kevinslin
Copy link

in case folks were curious - there is now alpha support for s3 exporter in opentelemetry-collector-contrib

@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Oct 22, 2023
Copy link
Contributor

This issue was closed because it has been marked as stale for 30 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 26, 2023
@mhausenblas mhausenblas reopened this Nov 27, 2023
@mhausenblas mhausenblas removed the stale label Nov 27, 2023
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Mar 31, 2024
@odeke-em
Copy link

@Aneurysm9 @mhausenblas howdy howdy? I can take on this issue and bring in the exporter that was implemented in https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/awss3exporter

@github-actions github-actions bot removed the stale label Apr 28, 2024
@mhausenblas
Copy link
Member

Thanks for your offer @odeke-em, much appreciated. However, this component is not on our short term roadmap, yet.

Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@mariusdrodten
Copy link

Thanks for your offer @odeke-em, much appreciated. However, this component is not on our short term roadmap, yet.

Hi,
Is there any update on it?
Or is there a way to use the opentelemetry collector builder to add this exporter to this distribution?

Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ADOT collector ADOT Collector related issues exporter Exporter related feature-request Feature request stale
Development

No branches or pull requests

5 participants