# Long ECS-Logged error.stack\_trace not shown in Kibana-Discover Document-Table

**URL:** <https://discuss.elastic.co/t/long-ecs-logged-error-stack-trace-not-shown-in-kibana-discover-document-table/277222>\
**Category:** Kibana\
**Created:** [June 28, 2021, 12:14pm UTC](https://discuss.elastic.co/t/long-ecs-logged-error-stack-trace-not-shown-in-kibana-discover-document-table/277222 "2021-06-28T12:14:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cproinger\_rbigroupit](https://avatars.discourse-cdn.com/v4/letter/c/dc4da7/32.png) [@cproinger\_rbigroupit](https://discuss.elastic.co/u/cproinger_rbigroupit)\
**Post date:** [June 28, 2021, 12:14pm UTC](https://discuss.elastic.co/t/long-ecs-logged-error-stack-trace-not-shown-in-kibana-discover-document-table/277222/1 "2021-06-28T12:14:38Z")

</div>

The problem is the following: Our Applications use ECS-Logs ([Overview | Elastic Common Schema (ECS) Reference [1.10] | Elastic](https://www.elastic.co/guide/en/ecs/current/ecs-reference.html)) to be indexed by filebeat. We use the default configuration which uses an "ignore\_above: 1024" setting to process "error.stack\_trace"-keyword fields which has an extended field "error.stack\_trace.text" which is of type "text".

```auto
      "error": {
        "properties": {
          "code": {
            "ignore_above": 1024,
            "type": "keyword"
          },
          "id": {
            "ignore_above": 1024,
            "type": "keyword"
          },
          "message": {
            "norms": false,
            "type": "text"
          },
          "stack_trace": {
            "fields": {
              "text": {
                "norms": false,
                "type": "text"
              }
            },
            "ignore_above": 1024,
            "index": false,
            "type": "keyword"
          },
          "type": {
            "ignore_above": 1024,
            "type": "keyword"
          }
        }
      },

```

In Kibana stacktraces with \<1024 bytes are displayed correctly in the table-view of the document. But when the size of the stacktrace exceeds this limit, neither "error.stack\_trace" (which is to be expected) nor "error.stack\_trace.text" is shown. So i have no way to see the properly formatted (newlines, tabs translated to html) stacktrace. I can just see it in the json-view (string content with "\n\t...").

I would like to have some advice to handle this. Otherwise our ELK-Stack solution is quite unusable for these situations.

best regards

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 26, 2021, 12:15pm UTC](https://discuss.elastic.co/t/long-ecs-logged-error-stack-trace-not-shown-in-kibana-discover-document-table/277222/2 "2021-07-26T12:15:25Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.