What steps are necessary to identify the cause of this phenomenon?

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? (Choose two.)
A. Ensure that file permissions for monitored files that allow the CloudWatch Logs agent to read the file have not been modified.
B. Verify that the OS Log rotation rules are compatible with the configuration requirements for agent streaming.
C. Configure an Amazon Kinesis producer to first put the logs into Amazon Kinesis Streams.
D. Create a CloudWatch Logs metric to isolate a value that changes at least once during the period before logging stops.
E. Use AWS CloudFormation to dynamically create and maintain the configuration file for the CloudWatch Logs agent.

amazon-exams

One thought on “What steps are necessary to identify the cause of this phenomenon?

  1. The situation described involves CloudWatch Logs agent successfully delivering logs initially but then stopping after a specific number of hours. To identify the cause of this issue, you should perform the following steps:

    A. Ensure that file permissions for monitored files that allow the CloudWatch Logs agent to read the file have not been modified. – Correct. Changes in file permissions might be causing the CloudWatch Logs agent to lose access to the log files.

    B. Verify that the OS Log rotation rules are compatible with the configuration requirements for agent streaming. – Correct. Incompatibility between log rotation rules and the CloudWatch Logs agent’s configuration can lead to logs being rotated and not delivered properly.

    C. Configure an Amazon Kinesis producer to first put the logs into Amazon Kinesis Streams. – Not relevant. Using Amazon Kinesis is not a direct solution for diagnosing why logs stop being delivered.

    D. Create a CloudWatch Logs metric to isolate a value that changes at least once during the period before logging stops. – This option might help you monitor and detect issues but isn’t a step to identify the cause.

    E. Use AWS CloudFormation to dynamically create and maintain the configuration file for the CloudWatch Logs agent. – This option is about managing configurations, not about diagnosing the issue.

    So, the correct answers are A and B. These steps will help you identify and address potential issues with permissions and log rotation rules that may be causing the problem with log delivery in CloudWatch Logs.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.