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

Feature request: Add cloudwatch metrics receiver #6226

Closed
yotamloe opened this issue Nov 10, 2021 · 4 comments
Closed

Feature request: Add cloudwatch metrics receiver #6226

yotamloe opened this issue Nov 10, 2021 · 4 comments
Assignees
Labels
closed as inactive comp:aws AWS components comp:aws-cw AWS CW related issues enhancement New feature or request Stale

Comments

@yotamloe
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We need an easy solution to import metric data from cloudwatch to Prometheus remote write compatible backend without using an exporter

Describe the solution you'd like
A receiver component That uses cloudwatch getmeticstatistics/getmetricdata API
reference:

Describe alternatives you've considered
Options:

  • Using external exporter with Prometheus and Prometheusexec receivers, for example: prom/cloudwatch-exporter, nerdswords/yet-another-cloudwatch-exporter
  • Using another agent (telegraf) but their plugin is buggy and has some limitations (importing tags). Besides that, we would love to stay with one agent like open telemetry for all of our telemetry data (logs, metrics, traces) going forward.

General notes
Are there any plans to develop this kind of receiver? I would love the feedback of our community if anyone has more recommendations or other possible solutions, also I would be happy to help implement such a solution.

@alolita alolita added comp:aws-cw AWS CW related issues enhancement New feature or request comp:aws AWS components labels Nov 10, 2021
@khanhntd
Copy link
Contributor

Hey @alolita would it possible for me to try this?

@alolita
Copy link
Member

alolita commented Jan 20, 2022

Hi @yotamloe we're taking a look at this and assessing feasibility. Stay tuned.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2022

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
Copy link
Contributor

github-actions bot commented Apr 6, 2023

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed as inactive comp:aws AWS components comp:aws-cw AWS CW related issues enhancement New feature or request Stale
Projects
None yet
Development

No branches or pull requests

3 participants