- Newest
- Most votes
- Most comments
Considering CloudWatch is a push based service, meaning that it just receives data and visualises it, absence of data to display indicates a possible issue with the service where data is published from (eg. CW Agent or an AWS Service). To confirm if the service published the data to CloudWatch, resources such as CloudTrail can be analysed to track API calls associated with your log setup.
Although, please note that the ‘NextSequenceToken’ field has been deprecated. The sequence token is now ignored in PutLogEvents actions. PutLogEvents actions are always accepted even if the sequence token is not valid. You can use parallel PutLogEvents actions on the same log stream and you do not need to wait for the response of a previous PutLogEvents action to obtain the nextSequenceToken value.
Reference : https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutLogEvents.html
Which indicates that it would not entirely mean the previous logs were received. Although, for every API call made via SDK or CLI etc. if the --debug option is enabled, a request ID would be generated along with the timestamp, that can help in investigating the root cause of it. Hence I would recommend reaching out to us via support case incase you would like to troubleshoot the issue further.
If CloudWatch agent is the source for pushing the logs, please refer to the following documentation which may be of additional help :
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/troubleshooting-CloudWatch-Agent.html
Relevant content
- Accepted Answerasked 2 years ago
- asked 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago