News for hackers. Stuff that matters.
Re:FreeBSD/EC2 on C5 instances by _msw_ on Friday November 17, 2017 @01:56PM (#15724903)
This is a topic that we're continuing to iterate on between EBS, CloudWatch, and the AWS console team for metrics. When a newly introduced behavior makes step function changes in graphs displayed in the AWS console it doesn't meet the principle of least astonishment.

We're also continuing to investigate the reported latency in the console. Because this is a derived metric from VolumeTotal{Read,Write}Time and Volume{Read,Write}Ops, there may be a miscalculation happening due to the change in dimensions.

Re:FreeBSD/EC2 on C5 instances by cperciva on Friday November 17, 2017 @03:07PM (#15725564)
Not sure if this is related, but when I was getting EFS working last year I noticed that CloudWatch graphs were often complete nonsense due to EFS not logging zeroes for idle filesystems but CloudWatch treating this as "missing data" rather than "implied zeroes".