AWS Lambda CloudWatch未能反序列化日志消息

Question

我们遇到了AWS Lambda和CloudWatch的问题：当它试图将计费详细信息记录到控制台时失败：

REPORT RequestId: ae61585c-9bda-480f-94e6-5b72f4ed7b17  Duration: 319.40 ms Billed Duration: 1257 ms    Memory Size: 3072 MB    Max Memory Used: 161 MB Init Duration: 936.79 ms    
XRAY TraceId: 1-60ad0933-538a058068ffb9c91b0a0db9   SegmentId: 58c34b0d2f79867e Sampl
[2021-05-25T14:32:07.412Z ERROR cloudwatch_lambda_agent::logs::logs_server] Failed to deserialize log message.
Err(Error("expected value", line: 1, column: 375))

[
{
"time": "2021-05-25T14:27:01.598Z",
"type": "platform.end",
"record": {
"requestId": "ae61585c-9bda-480f-94e6-5b72f4ed7b17"
}
}
,{"time":"2021-05-25T14:27:01.598Z","type":"platform.report","record":{"requestId":"ae61585c-9bda-480f-94e6-5b72f4ed7b17","metrics":{"durationMs":319.40,"billedDurationMs":1257,"memorySizeMB":3072,"maxMemoryUsedMB":161,"initDurationMs":936.79},"tracing":}}}]

它几周前就开始失败了，显然，AWS方面有一个错误。有人遇到过同样的错误吗？

Answer 1

从错误消息来看，问题可能是由于在Lambda上启用了活动跟踪，并且跟踪信息无法发送到AWS X射线服务器(或者无法解释消息(。在我的环境中，将活动跟踪从活动更改为传递解决了问题。问题似乎从根本上在于AWS本身，所以我认为您应该联系AWS支持。