- 最新
- 投票最多
- 评论最多
I would look to restart the service and if it continues then check the CWAgent log in C:\ProgramData\Amazon to see what the cause is.
Hello,
Cloud-watch-agent does the below: Collect internal system-level metrics from Amazon EC2 instances across operating systems. The metrics can include in-guest metrics, in addition to the metrics for EC2 instances. The additional metrics that can be collected are listed in Metrics collected by the CloudWatch agent.
Collect system-level metrics from on-premises servers. These can include servers in a hybrid environment as well as servers not managed by AWS.
Retrieve custom metrics from your applications or services using the StatsD and collectd protocols. StatsD is supported on both Linux servers and servers running Windows Server. collectd is supported only on Linux servers.
Collect logs from Amazon EC2 instances and on-premises servers, running either Linux or Windows Server.
However, to determine on why 100% CPU is utilized, you might have to reach out to the AWS Support team to try and check your EC2 level metrics and determine if it was due to an issue related to the VM or whether actually high CPU workload was handled by the CW agent to have such a high CPU. Hope this helps.
相关内容
AWS 官方已更新 2 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
Hi, Thank you for the answer. May I possibly ask what kind of logs should I delete. there are too many logs in the file and I'm not so sure which logs should I delete.
I wasn’t suggesting you delete the logs. You need to open the CWAgent log to see if there is an obvious cause. Have you restarted the agent to see if that resolves it?