- Newest
- Most votes
- Most comments
I Could not catch you properly, but here are some details - CloudWatch agent has these steps to make it work - 1. Install 2. Fetch Configure with JSON/SSM 3. Start agent. Also you can enable autostart of agent on Windows Service/ systemctl enable servicename in Linux to autostart it.
If it fails / stops for some reason - it could be less memory available. As solution - You can set a Cron in Linux/ Task scheduler in Windows to start the agent every 1 minute.
Also you can check the Logs of CloudWatch agent on server in default location of installation.
Hi, you should connect to your EC2 instance and type the command indicated on this page https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/ReportCWLAgentStatus.html
so either
sudo service awslogs status
or if Linux AL2
sudo service awslogsd status
and then Check the /var/log/awslogs.log file for any errors, warnings, or issues with the CloudWatch Logs agent
I have used the command and it is showing this "unit awslogsd.service could not be found"
Relevant content
- asked 3 years ago
- asked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- published 2 years ago
yes , i have did this steps (1. Install 2. Fetch Configure with JSON/SSM 3. Start agent.) ihave also checked all the utilization (memory,CPU....) everything is fine and working properly ,also there are no taskscheduler or any automatuion which can conflict ! is there any other solution ?