-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Quite a few incoming logs are not correctly parsed.
This is a fairly typical example:

In this example I cannot tell why the message field is not parsed.
Here an example where everything works fine:

Here some messages that fail to parse as text:
{"ip_address":"192.168.88.23","device_name":"summer-haze","device_type":"raspberrypi4-64","application":"Garden","message":"Aug 07 11:29:14 364a735 d970cdcf711a[1379]: 2020-08-07T11:29:14.054Z v3.0.45 pid[8] Memory stats: heapUsedMB=17 heapTotalMB=19 memoryRssMB=64
"}
{"ip_address":"10.65.1.82","device_name":"rough-haze","device_type":"raspberrypi4-64","application":"Garden","message":"Aug 07 11:28:52 ee828e3 2471bd964183[1423]: [event] Event: Service kill {"service":{"appId":1685824,"serviceId":642853,"serviceName":"logspooler","releaseId":1488795}}"}
You can find the complete project in Github - including Dockerfiles and docker-compose that start logagent and the logspooler that tails a log file into logagent.