Concourse v3.14.1 log structure discrepancy


#1

Hi guys, I’m seeing inconsistent log structures on Concourse v3.14.1

Here’s an example:

{"timestamp":"1542018614.581978321","source":"atc","message":"atc.syncer.logging:radar.scanresources-runner-error","log_level":1,"data":{"error":{"Offset":0},"session":"35.153"}}
{"timestamp":"1542021966.316760063","source":"guardian","message":"guardian.api.garden-server.get-property.failed","log_level":2,"data":{"error":"property does not exist: concourse:exit-status","handle":"fbbxxb54-ddbf-4bdb-4406-173362377a49","session":"3.1.848541"}}

The differing structure of the data.error key is messing with my logging setup. Sometimes it’s an object and sometimes it’s a string. It required unnecessary filtering/modifying the json or completely ignoring these logs form being collected (which is also undesirable).

Is this discrepancy on v4 too?