New component: AWS Timestream Exporter

[fredthomsen]

The purpose and use-cases of the new component

AWS Timestream Exporter send data to the AWS Timestream metric store. Timestream is a time-series serverless database for storing and analyzing metrics in the AWS platform. There are a number of analytics use cases, for example the data stored in Timestream can be used by various AWS products, like SageMaker, and/or visualized in Graphana. Lifecycle management per metric datapoint is also supported.

Example configuration for the component

awstimestream:
  database: sample-db
  table: sample-table
  region: us-east-1

Telemetry data types supported

metrics

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute this as a representative of the vendor.

Sponsor (optional)

No response

Additional context

Currently we have developed this for internal use and need to make things more generic and configurable, hence the current configuration above is fairly barebones.

[codeboten]

@Aneurysm9 @bryan-aguilar is this a component folks from AWS would be interested in sponsoring?

[github-actions]

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[fredthomsen]

Without a sponsor from AWS, looking at the language in https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components, I assume this is a no-go. I'll let this sit a bit longer, and if there is no sponsor, we'll open source this in our own repo.

[Gaganjuneja]

Any update on this?

[fredthomsen]

@Gaganjuneja we are likely moving away from timestream usage and thus I am hesitant to open source in our own company repo given that it would languish, so I'd rather do it here, but again there is no sponsor.

[github-actions]

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.