Amazon CtoudWatch Logs agent is successfully delivering logs lo the CloudWatch Logs service. However, logs stop being delivered after the associated log stream has been active for a specific number…

Question

Options

• AEnsure that file permissions for monitored files that allow the CloudWatch Logs agent to read the
• BVerify that the OS Log rotation rules are compatible with the configuration requirements for agent
• CConfigure an Amazon Kinesis producer to first put the logs into Amazon Kinesis Streams.
• DCreate a CloudWatch Logs metric to isolate a value that changes at least once during the period
• EUse AWS CloudFormation to dynamically create and maintain the configuration file for the

• A
  85% (46)
• C
  7% (4)
• D
  4% (2)
• E
  4% (2)

Explanation

Ensure that file permissions for monitored files that allow the CloudWatch Logs agent to read the file have not been modified. If the file permissions of the monitored files are changed, the CloudWatch Logs agent may no longer have the ability to read the logs, which would stop log delivery. Verify that the OS log rotation rules are compatible with the configuration requirements for agent Log rotation could result in the monitored file being renamed or moved, which would disrupt the agent's ability to read and stream logs. Ensuring that the rotation rules are compatible with the CloudWatch Logs agent will help resolve this issue. These steps address potential file permission changes and log rotation, both of which could cause the logging to stop after a certain period of time.

No community discussion yet for this question.