Brandon Walton @blw9u2012 06:02
@ks888 i'm having issues with displaying metrics from our target groups. It displays the correct graph but the Y axis is only showing a range between 0 and 1. Am i goofing somewhere?
i want to display the Y axis in milliseconds
i've added a metric from the AWS/ApplicationELB namespace and added the TargetResponseTime metric name and dimension for one of our load balancers
Kishin Yagami @ks888 22:35
@blw9u2012 Thank you for asking. The data points are averaged over 5 minutes when the 'Day' time frame is selected. Perhaps the maximum value of your data points is higher than 1.0, but the maximum value of the AVERAGED values is lower than 1.0.
Or, the rounded value in the tooltip may be the problem. Even if the actual value is 0.01, the value in the tooltip is rounded and will be 0. Such a behavior seems incovenient in your case, so it should be fixed.
Brandon Walton @blw9u2012 23:09
@ks888 thanks for responding! I also looked into the metrics and the unit that the metric TargetResponseTime returns is in seconds vs the latency metric in the demo site being milliseconds. I don't think that you can specify another unit to be returned other than seconds. I thought that this possibly could be related but it sounds like the latter issue you described. In any event thanks for responding!
From @blw9u2012's comment on gitter:
Brandon Walton @blw9u2012 06:02 @ks888 i'm having issues with displaying metrics from our target groups. It displays the correct graph but the Y axis is only showing a range between 0 and 1. Am i goofing somewhere? i want to display the Y axis in milliseconds i've added a metric from the AWS/ApplicationELB namespace and added the TargetResponseTime metric name and dimension for one of our load balancers
Kishin Yagami @ks888 22:35 @blw9u2012 Thank you for asking. The data points are averaged over 5 minutes when the 'Day' time frame is selected. Perhaps the maximum value of your data points is higher than 1.0, but the maximum value of the AVERAGED values is lower than 1.0. Or, the rounded value in the tooltip may be the problem. Even if the actual value is 0.01, the value in the tooltip is rounded and will be 0. Such a behavior seems incovenient in your case, so it should be fixed.
Brandon Walton @blw9u2012 23:09 @ks888 thanks for responding! I also looked into the metrics and the unit that the metric TargetResponseTime returns is in seconds vs the latency metric in the demo site being milliseconds. I don't think that you can specify another unit to be returned other than seconds. I thought that this possibly could be related but it sounds like the latter issue you described. In any event thanks for responding!