Issues with JSON formatted logs

[jalenplayvs]

Migrating from LogDNA-agent to the Lambda integration, our JSON logs are not properly formatted in the LogDNA web app. The JSON body gets converted to a string, and log lines displayed in the web app as a string.

In the interim, we made our own fork with a hacky fix that would break other use-cases. But we would like the upstream package to have better support for JSON formatted logs so that we do not have to maintain a patch.

Setup: Follow these instructions (NOTE: The link to the zip file is an old version sitting in an S3 bucket, we downloaded the latest from github). We did port the instructions to Terraform, it is possible that something is different than what the manual instructions would produce, but I could not find a meaningful difference.

Steps to reproduce:

• Run an application with JSON formatted logs, ingest logs using LogDNA agent
• Run the same application, use the Cloudwatch->Lambda->LogDNA integration to ingest

Expected result: The log lines look the same in the LogDNA web app

Actual result: The logs lines look different, are not properly parsed as JSON data

[smusali]

Sorry for the late reply, @jalenplayvs, and thanks a lot for reporting this use case!

We will bring this enhancement to our lambda function as soon as possible and keep you updated!

[madarve]

Hi, Is there any movement on this?

[steve-scx]

This does seem to be fixed in version v2.2.1. Try using LOG_RAW_EVENT=TRUE.