Error without origin


We're running ECK and our 7.9.3 Filebeat are logging a lot of messages like these:

{"log.level":"error","@timestamp":"2020-11-25T09:43:39.424Z","log.logger":"reader_json","log.origin":{"":"readjson/json.go","file.line":57},"message":"Error decoding JSON: json: cannot unmarshal number into Go value of type map[string]interface {}","ecs.version":"1.5.0"}

The problem is, it doesn't tell anything about which event it's trying to unmarshal and which log file it's coming from. Is there any way to set up filebeat to include the origin of an event in these kinds of errors? Or the entire string it's trying to unmarshal?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.