Skip to content

Fix exception structure in JSON logging

Tan Le requested to merge fix-exception-logging-format into main

The existing exception keys are treated as a whole string instead of a nested exception object. This possibly causes issues with ingesting these log entries to ElasticSearch.

Before

{
  "exception.message": "[StatusCode.UNAVAILABLE]...",
  "exception.backtrace": "Traceback...",
}

After

{
  "exception": {
    "message": "[StatusCode.UNAVAILABLE]...",
    "backtrace": "Traceback..."
  }
}

Closes #196 (closed)

Edited by Alexander Chueshev

Merge request reports