1 個回答
- 最新
- 最多得票
- 最多評論
0
Hi, I guess that you're speaking of logs written by your own code (not those written by lambda runtime). In that case, I would create a CloudTrail track to locate all calls to CW APIs by your Lambda and see if they are all present (by comparing to the Lambda invocation unique ids).
If calls to CW match Lambda invocations, then it may be an issue with CW itself for which more investigation will be needed. Otherwise, it's the application code that may not handle CW logging properly.
Additionally, I'd sugggest to mirror the calls to CW with equivalent messages in a SQS queue to see if they match
Best,
Didier
相關內容
- AWS 官方已更新 2 年前
- AWS 官方已更新 4 年前