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

Automatically set CloudWatch graph yaxis unit #13575

Closed
mtanda opened this issue Oct 9, 2018 · 2 comments
Closed

Automatically set CloudWatch graph yaxis unit #13575

mtanda opened this issue Oct 9, 2018 · 2 comments

Comments

@mtanda
Copy link
Collaborator

mtanda commented Oct 9, 2018

Like stackdriver datasource, I want to set yaxis unit automatically.

GetMetricStatistics API response the metrics Unit.
https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html
https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_Datapoint.html

By using this information, Grafana can set yaxis unit.

@marefr marefr changed the title [Feature Request] Automatically set CloudWatch graph yaxis unit Automatically set CloudWatch graph yaxis unit Oct 10, 2018
@marefr marefr closed this as completed in 5f69854 Oct 10, 2018
@marefr marefr added this to the 5.4 milestone Oct 10, 2018
marefr added a commit that referenced this issue Oct 10, 2018
@marefr marefr modified the milestones: 5.4, 5.3 Oct 10, 2018
marefr added a commit that referenced this issue Oct 10, 2018
@chipironcin
Copy link

Hi contributors,
This feature is useful for most. Unfortunately I encountered a use case where this functionality will limit the user ability to display the data.

I am registering in CloudWatch a hit per "request" to my API, storing the time it took to process it as the metric value. The units for these values are "time" units so Grafana auto detects "ms".

Because of that, I am unable to change my units to "seconds" for example. And some of my graphs used to display the hits "count", setting the metric as "sampleCount". Because of the new enforced "unit" it is not possible to properly represent the hits count because they are not in "ms".

Any ideas on how to overcome this limitation? Am I missing something?
Maybe this feature requires further refinement?

@chipironcin
Copy link

Ok, seems the problem I described is being tracked at #13733

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants