If you update your CloudWatch agent configuration file, the next time that you start theĪgent, you need to use the fetch-config option.
My agent configuration but don’t see the new metrics or logs in the CloudWatch console
Including the namespace field, see CloudWatch agentĬonfiguration file: Metrics section. For more information about the configuration file, Use the configuration wizard, the agent configuration file output from the wizard is namedĬonfig.json. Ran the configuration wizard, or you might have moved it to a different directory.
When you first download the CloudWatch agent package, the agent configuration file isĪmazon-cloudwatch-agent.json. If you don't see the metrics that you expect, check theĬonfiguration file to confirm the namespace being used. Namespace using the namespace field in the metrics section of theĪgent configuration file. Namespace for metrics collected by the agent is CWAgent. If the CloudWatch agent has been running but you can't find metrics collected by it in theĪWS Management Console or the AWS CLI, confirm that you're using the correct namespace. For more information, seeĬonfiguration for proxy or Region information. If you don’t have a credential file, you must create one. Settings\\Administrator\\.aws on Windows Server 2003, you can specify your ownĬredential path by using the shared_credential_file option in $SystemDrive\\Users\\Administrator\\.aws on Windows Server 2012, or “$SystemDrive\\Documents and On Windows Server, if you have credentials in a location other than For more information, seeĪ service does not start, and events 70 are logged in the Windows event log. To fix this issue, increase the service timeout value. This causes the agent to fail with an error similar to the following: Because Windows Server, by default, allows only 30 seconds for services to start, Windows Server installations, the CloudWatch agent takes more than 30 seconds to If the server service is already running, the following may be the issue. If the agent tries to start when the server service isn't running. To fix this, first make sure that the server service is running. + FullyQualifiedErrorId : CouldNotStartService, + CategoryInfo : OpenError: (:ServiceController) , Start-Service : Service 'Amazon CloudWatch Agent (AmazonCloudWatchAgent)' cannot be started due to the followingĮrror: Cannot start service AmazonCloudWatchAgent on computer '.'.Īt C:\Program Files\Amazon\AmazonCloudWatchAgent\amazon-cloudwatch-agent-ctl.ps1:113 char:12