Topic 1 Question 233
2 つ選択Amazon CloudWatch Logs agent is successfully delivering logs to the CloudWatch Logs service. However, logs stop being delivered after the associated log stream has been active for a specific number of hours.
What steps are necessary to identify the cause of this phenomenon?
Ensure that file permissions for monitored files that allow the CloudWatch Logs agent to read the file have not been modified.
Verify that the OS Log rotation rules are compatible with the configuration requirements for agent streaming.
Configure an Amazon Kinesis producer to first put the logs into Amazon Kinesis Streams.
Create a CloudWatch Logs metric to isolate a value that changes at least once during the period before logging stops.
Use AWS CloudFormation to dynamically create and maintain the configuration file for the CloudWatch Logs agent.
ユーザの投票
コメント(4)
- 正解だと思う選択肢: AB
AB E is not the step to identify the cause but can potentially solve the issue.
👍 2Bachhu2025/01/04 - 正解だと思う選択肢: BE
To identify the cause of logs stopping after a certain number of hours, you should:
B. Verify that the OS Log rotation rules are compatible with the configuration requirements for agent streaming.
E. Use AWS CloudFormation to dynamically create and maintain the configuration file for the CloudWatch Logs agent.
These steps will help ensure that the log rotation process isn't interfering with the CloudWatch Logs agent and that the configuration is properly maintained
👍 1IPLogic2024/12/05 The question asks "What steps are necessary to identify the cause of this phenomenon? ". E is not a step to identify the cause, but an action to potentially solve the issue. So, should be A, B. For A, file permissions CAN change to prevent the Cloudwatch agent from reading it.
👍 1nznzwell2024/12/22
シャッフルモード