# Extra chars in kibana message field

**URL:** <https://discuss.elastic.co/t/extra-chars-in-kibana-message-field/199158>\
**Category:** Kibana\
**Created:** [September 12, 2019, 12:59am UTC](https://discuss.elastic.co/t/extra-chars-in-kibana-message-field/199158 "2019-09-12T00:59:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![O\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/o_k/32/52424_2.png) [@O\_K](https://discuss.elastic.co/u/O_K)\
**Post date:** [September 12, 2019, 12:59am UTC](https://discuss.elastic.co/t/extra-chars-in-kibana-message-field/199158/1 "2019-09-12T00:59:56Z")

</div>

Hello,

Do you know how to deal with these extra chars which don't allow to parse log entries properly?

elasticsearch log format contains extra chars like `[0;39m`, `e[33m` :

```auto
e[2m2019-09-11 20:45:43.600e[0;39m e[33m WARNe[0;39m e[35m27e[0;39m e[2m---e[0;39m e[2m[nio-8070-exec-9]e[0;39m e[36me.i.k.k.v.validator.Validator e[0;39m e[2m:e[0;39m #/verifiableCredential/5/credentialSubject: required key [id] not found

```

kubernetes stdout log output format looks pretty clean:

```auto
2019-09-11 00:22:53.938 WARN 27 --- [nio-8060-exec-9] o.z.p.spring.web.advice.App : Not Found: Not such consent by vmk dataset id: 123

```

---

<div class="post-metadata">

**Author:** ![VietCong](https://avatars.discourse-cdn.com/v4/letter/v/e47774/32.png) [@VietCong](https://discuss.elastic.co/u/VietCong)\
**Post date:** [September 12, 2019, 2:32am UTC](https://discuss.elastic.co/t/extra-chars-in-kibana-message-field/199158/2 "2019-09-12T02:32:49Z")

</div>

`e[2m2019-09-11 20:45:43.600e[0;39m e[33m WARNe[0;39m e[35m27e[0;39m e[2m---e[0;39m e[2m[nio-8070-exec-9]e[0;39m e[36me.i.k.k.v.validator.Validator e[0;39m e[2m:e[0;39m #/verifiableCredential/5/credentialSubject: required key [id] not found`

Does this line of log happens after the logstash parser? if so, can you share the pipeline including the input, filter, output parts of the pipeline?

---

<div class="post-metadata">

**Author:** ![O\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/o_k/32/52424_2.png) [@O\_K](https://discuss.elastic.co/u/O_K)\
**Post date:** [September 15, 2019, 7:12am UTC](https://discuss.elastic.co/t/extra-chars-in-kibana-message-field/199158/3 "2019-09-15T07:12:15Z")

</div>

solved it with **\x1B** ESC

---

<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:** [October 13, 2019, 7:12am UTC](https://discuss.elastic.co/t/extra-chars-in-kibana-message-field/199158/4 "2019-10-13T07:12:15Z")

</div>

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