Indexing of Log Output for Self Hosted Kubernetes Deployment

Hi,

I have deployed Retool to kubernetes using your provided helm charts. However the logging that the pods generate is causing a few issues in the ES index I am sending them to.

Basically the message field in the logs is sometimes structured as an object. So message.Memory Stats for container.freeSystemMemory or message.Memory Stats for process.percentageHeapUsed for example. But in other logs its just a String.

The ES index is having issues because the field is arriving and being identified as different types.

As a bandaid I have disabled logging with the environment variable LOG_LEVEL: "OFF" but I am hoping there is a way to remove the JSON encoding from the logs and just output "plain" logs.

Hey @luke2! Unfortunately, right now there are no configuration options for the logging. I have submitted an internal ticket to track this request, and can update you as I get any additional in information.

I just upgraded to 3.75.12-stable and LOG_LEVEL: "OFF" no longer seems to work. Is there any way this can be re-enabled?

1 Like

Hey @luke2! Welcome back to the community. :slightly_smiling_face:

You may already be aware, but we don't encourage setting LOG_LEVEL to anything below info. For those edge cases that require an exception, the levels below that are currently warn, error, and fatal.

I can't say for sure whether the issue you originally raised has been addressed, but it's worth verifying before suppressing the logs again. I'll check on the status of that particular request and additionally talk to the team about re-adding the off level, if you end up still needing it. :+1: