Learn more about AWS Management and Governance at - amzn.to/2JkjbBk In this video we show you how you configure and deploy the CloudWatch Agent, collect metrics and logs from your Windows instances and provide actionable data.
One key thing to note while answering to questionnaire from cloudwatch agent wizard is the question related to "collectD". If we blindly accept the default value of "Yes" and if that "collectD" binary is not installed on that EC2 instance then the agent will not start in the end during the run command execution on Systems Manager. I got this error -> "Error running agent: Error parsing /opt/aws/amazon-cloudwatch-agent/etc/amazon-cloudwatch-agent.toml, open /usr/share/collectd/types.db: no such file or directory". I had faced this issue and was finally able to debug its root cause. Either we have to say "no" to that question or install the binary on EC2 instance or we can create this dummy folder and file by executing mkdir -p /usr/share/collectd/ touch /usr/share/collectd/types.db on instance to resolve the issue
Is there a way to get memory of db instance class For example db.r5.large = 16GB This data is present in hardware specifications. But is there a way to get it using Boto?
Thanks Sir, but bit confusion, I am IAM user having admin permission, So i can or only root user to perform this ? how to do in Linux CentOs1. it is the same steps to follow for disk and mem metric?
Hi, users can have consolidated monitoring for multiple accounts. This account today is only accessible via Administrator Access role and need a solution to allow non-admin users to this account and also need permissions to create Cross-Account-Cross-Region Dashboards. How this can be done?
Thank you for this. I carefully followed your instructions in the video, but unable to view the IISLogs and EventLog-System. Will they automatically appear after you configuration or will you create a log group named IISLogs?
I created the IISLogs and tried to search for Log Group but it says "No events found. It appears you have not installed a CloudWatch Logs agent or there are no events available at the moment. Try to install the agent or try later."