opt/aws/amazon-cloudwatch-agent/logs/amazon-cloudwatch-agent.log %PROGRAMDATA%\Amazon\SSM\Logs\audits\amazon-ssm-agent-audit-YYYY-MM-DD %PROGRAMDATA%\Amazon\SSM\Logs\amazon-ssm-agent.log $Env:ProgramData\Amazon\AmazonCloudWatchAgent\Logs\amazon-cloudwatch-agent.log etc/nf file to determine the specific setup for your system's log You should monitor, but you should check the /etc/nf or The following table defines the common default log files that The system, application, and security logs for Linux systems are typically stored in the YouĬan choose which Windows event logs you want to monitor (for example System, The CloudWatch agent supports monitoring Windows event logs by providing the event log name. The OS-generated log files might be different depending on the OS version. Your log capture approach should include any system and security logs generatedīy the OS. System-level logs are essential for diagnosing and troubleshooting issues on premises or on You can automatically retrieve and apply these configurations An example of an S3 bucket setup for this purpose isĬonfigurations section of this guide. They can be retrieved by your EC2 instances. These unique configuration files should be separately stored in an S3 bucket where Logs and metrics can be defined in separate CloudWatch configuration files and appended to the standardĬonfiguration. We recommend that you use the CloudWatch configuration file wizard or configuration file schema to define the CloudWatch agentĬonfiguration file for each OS that you plan to support. Systems-level metrics and logs are a central component of a monitoring and logging solution,Īnd the CloudWatch agent has specific configuration options for Windows and Linux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |