Uploaded image for project: 'Thorntail'
  1. Thorntail
  2. THORN-283

Improve stack trace support in Logstash fraction

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      ELK (Elasticsearch / Logstash / Kibana) is a popular stack for log aggregation and viewing.

      The Logstash support in Swarm outputs stack traces in a format that Kibana does not understand.

      Proposed is to output stack traces as a formatted string/text block rather than a JSON array of json objects of exception stack frames.

      Additionally, I think "caused by" exceptions are currently lost in the current implementation as well, making stack traces much less useful for determining root cause.

      The actual exception class (e.g. java.lang.NullPointerException) is also absent from the log

      Kibana also issues a warning that JSON objects inside text fields are not very well supported

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jhovell John Hovell
              • Votes:
                2 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: