[英]How can I tell if CPUUtilization in AWS is the reason my website sign-up is timing out?
Our website is hosted on AWS in a t2.small instance. 我们的网站在t2.small实例中托管在AWS上。 User-facing sign-up is currently timing out.
目前,面向用户的注册正在超时。
Initially, I was getting a loadbalancer latency alarm notification for this instance, so I increased the limit, which seemed to work as a temporary solution. 最初,我收到此实例的负载平衡器延迟警报通知,因此我增加了限制,这似乎是一个临时解决方案。
However, once I increased the limit, I started getting 2 other alarm notifications, which were as follows: 但是,一旦增加了限制,便开始收到另外2条警报通知,如下所示:
1) production-remove-capacity-alarm
1)生产能力删除警报
Description: None
说明:无
Threshold: CPUUtilization <= 40 for 3 datapoints within 15 minutes
阈值:15分钟内3个数据点的CPUUtilization <= 40
2) AWSEBCloudwatchAlarmLow
2)AWSEBCloudwatchAlarmLow
Description: ElasticBeanstalk Default Scale Down alarm
说明:ElasticBeanstalk默认按比例缩小警报
Threshold: NetworkOut < 2,000,000 for 1 datapoints within 5 minutes
阈值:5分钟内NetworkOut <1,000,000个数据点<2,000,000
It seems to me that I should simply change the alarm notifications so that I'm no longer alerted to #2, as I don't see how this is interfering with anything, but please correct me if I seem to be missing something. 在我看来,我应该简单地更改警报通知,以使我不再受到2号警报的影响,因为我看不到这是如何干扰任何事物的,但是如果我似乎缺少任何东西,请更正我。
Regarding #1, does it seem likely that somehow adjusting CPU Utilization in AWS will solve the timeout issue with website sign-up? 关于#1,似乎可以通过某种方式在AWS中调整CPU使用率来解决网站注册超时问题?
And if so, what specifically ought to be done? 如果是这样,应该具体做什么?
Everything is okay. 一切正常。 Don't panic.
不要惊慌
The first priority is that your application operates correctly. 第一要务是您的应用程序正确运行。 Hopefully your adjustment to the instance type ) satisfactorily fixed this (but it is still worth watching).
希望您对实例类型( )的调整能够令人满意地解决此问题(但仍然值得一看)。
The above two alarms are basically saying: 以上两个警报基本上是在说:
These alarms can be used to scale-in instances (reduce the number of instances) so that you are not paying for excess capacity. 这些警报可用于扩大实例数量(减少实例数量),这样您就不必为多余的容量付费。 There would be similar alarms that let you scale-out (add additional instances).
会有类似的警报让您向外扩展 (添加其他实例)。
ALARM simply means the check is True . 警报仅表示检查为True 。 That is, the condition has been satisfied.
即,已经满足条件。 It does not necessarily indicate a problem.
它不一定表示有问题。
I'm going to presume that you currently have only one instance running. 我假设您当前仅运行一个实例。 If so, you can ignore those alarms (and Auto Scaling will ignore them too) because you are already at the minimum capacity.
如果是这样,您可以忽略那些警报(并且Auto Scaling也将忽略它们),因为您已经处于最小容量。
If Auto Scaling has been configured to scale-out to more instances, these alarms would later scale-in to save you money. 如果已将Auto Scaling配置为横向扩展到更多实例,则这些警报稍后将横向扩展以节省您的资金。 They're probably a bit trigger-happy, only looking at 15 minutes CPU and 5 minutes of network traffic — it would normally be better to wait for a longer period before deciding to remove capacity.
他们可能会有点满意,只查看15分钟的CPU和5分钟的网络流量-通常最好等待更长的时间再决定删除容量。
Bottom line: If your application is running correctly and you are only operating a single instance, there's nothing to worry about. 底线:如果您的应用程序运行正常,并且您仅在运行一个实例,则无需担心。 It's all working as expected.
一切都按预期进行。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.