Cloud watch agent not able to sent logs

0

I have set up an AWS CloudWatch Logs log group for collecting and monitoring log data from various AWS resources and applications. However, I've encountered a situation where the log group exists, but no log streams are visible within it. I'm trying to troubleshoot this issue to ensure that log data is properly ingested and displayed.I am encountering an issue with the AWS CloudWatch Logs Agent in my log collection and forwarding setup. I've noticed the following warning messages in the log files:

2023-09-27 08:15:31,007 - cwlogs.push.reader - WARNING - 2502198 - Thread-4 - Fall back to previous event time: {'timestamp': 1686224709000, 'start_position': 2065936448L, 'end_position': 2065937098L}, previousEventTime: 1686224709000, reason: timestamp could not be parsed from message. 2023-09-27 08:15:31,007 - cwlogs.push.batch - WARNING - 2502198 - Thread-4 - Skip event: {'timestamp': 1686224709000, 'start_position': 2065936448L, 'end_position': 2065937098L}, reason: timestamp is more than 14 days in past. 2023-09-27 08:15:31,007 - cwlogs.push.reader - WARNING - 2502198 - Thread-4 - Fall back to previous event time: {'timestamp': 1686224709000, 'start_position': 2065937098L, 'end_position': 2065937223L}, previousEventTime: 1686224709000, reason: timestamp could not be parsed from message. 2023-09-27 08:15:31,007 - cwlogs.push.batch - WARNING - 2502198 - Thread-4 - Skip event: {'timestamp': 1686224709000, 'start_position': 2065937098L, 'end_position': 2065937223L}, reason: timestamp is more than 14 days in past. 2023-09-27 08:15:31,007 - cwlogs.push.reader - WARNING - 2502198 - Thread-4 - Fall back to previous event time: {'timestamp': 1686224709000, 'start_position': 2065937223L, 'end_position': 2065937544L}, previousEventTime: 1686224709000, reason: timestamp could not be parsed from message. 2023-09-27 08:15:31,008 - cwlogs.push.batch - WARNING - 2502198 - Thread-4 - Skip event: {'timestamp': 1686224709000, 'start_position': 2065937223L, 'end_position': 2065937544L}, reason: timestamp is more than 14 days in past.

To address this, I'm seeking guidance on the following:

  1. What are some common reasons for not seeing any log streams in a CloudWatch Logs log group, even though the log group itself is present?
  2. How can I verify that the applications and services generating the logs are correctly configured to send log data to the specified log group?
  3. Are there any recommended best practices for troubleshooting log stream visibility issues within CloudWatch Logs?
1 Answer
0

Hello, shivani.

Please follow this document https://repost.aws/knowledge-center/cloudwatch-push-logs-with-unified-agent that can help you troubleshoot your problem. Best regards, Andrii

profile picture
EXPERT
answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions