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

CloudWatch MetricsProvider implementation #984

Open
1 task done
aajtodd opened this issue Jul 18, 2023 · 0 comments
Open
1 task done

CloudWatch MetricsProvider implementation #984

aajtodd opened this issue Jul 18, 2023 · 0 comments
Labels
feature-request A feature should be added or improved. no-auto-closure We do not want this issue to be automatically closed. p2 This is a standard priority issue queued This issues is on the AWS team's backlog

Comments

@aajtodd
Copy link
Contributor

aajtodd commented Jul 18, 2023

Describe the feature

Currently only an OpenTelemetry based provider is available for TelemetryProvider/MetricsProvider. It would be useful to expose a "native" CW based MetricsProvider that exports directly to cloudwatch without needing to configure OTeL.

Is your Feature Request related to a problem?

Some customers may not want to depend on OTeL and desire a fully integrated AWS solution. OpenTelemetry also does client side aggregation of Histogram instruments which may not be desirable for some use cases. Java v2 enables finer resolution with detailed metrics.

Proposed Solution

There isn't currently any other TelemetryProvider other than OTeL. We would probably want to implement a generic SDK provider that can be adapted to work for CW and potentially other metric systems. There is a lot that goes into collecting, aggregating, and exporting that it should be mostly re-usable. Look to Java V2 SDK and OTeL for inspiration here:

e.g.

TelemetryProvider.build {
     metricsExporters += CloudwatchMetricsExporter(...)
     meterReader = PeriodicMeterReader(interval = 5.seconds)
}

Describe alternative solutions or features you've considered

We may be able to write our own metric exporter for OpenTelemetry, it's unclear at what level we have access to the actual data recorded from a MetricExporter. This of course still goes through OTeL but may be less involved to implement if the exporter has access to fine grained data (since OTeL is handling the metrics collection and plumbing, etc). It wouldn't require setting up an OTeL collector either, metrics would be exported directly from the application process.

Acknowledge

  • I may be able to implement this feature request

AWS Kotlin SDK version used

N/A

Platform (JVM/JS/Native)

N/A

Operating System and version

N/A

@aajtodd aajtodd added the feature-request A feature should be added or improved. label Jul 18, 2023
@ianbotsf ianbotsf added the no-auto-closure We do not want this issue to be automatically closed. label Dec 7, 2023
@RanVaknin RanVaknin added p2 This is a standard priority issue queued This issues is on the AWS team's backlog labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved. no-auto-closure We do not want this issue to be automatically closed. p2 This is a standard priority issue queued This issues is on the AWS team's backlog
Projects
None yet
Development

No branches or pull requests

3 participants