# After Updating Logstash to 7.7 from 7.6 regex isn't working the same

**URL:** <https://discuss.elastic.co/t/after-updating-logstash-to-7-7-from-7-6-regex-isnt-working-the-same/234012>\
**Category:** Logstash\
**Created:** [May 23, 2020, 5:31pm UTC](https://discuss.elastic.co/t/after-updating-logstash-to-7-7-from-7-6-regex-isnt-working-the-same/234012 "2020-05-23T17:31:01Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![andres-perez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andres-perez/32/136461_2.png) [@andres-perez](https://discuss.elastic.co/u/andres-perez)\
**Post date:** [May 25, 2020, 11:20am UTC](https://discuss.elastic.co/t/after-updating-logstash-to-7-7-from-7-6-regex-isnt-working-the-same/234012/9 "2020-05-25T11:20:16Z")

</div>

Hi!

Just to add more information, I think I have tackled similar issues in the past; maybe using the notation **`\x1B`** as the initial escape sequence is useful for your purpose.

Here is link to the information I compiled for a related issue:

> [@Parsing special charaters with grok](https://discuss.elastic.co/t/parsing-special-charaters-with-grok/213548/2):
>
> These codes are special [ANSI sequences](https://stackoverflow.com/a/33206814) used to change the color in terminal output. In simple words, these marks indicate to compatible console tools: start block of green characters INFO (end of the block and) return to default color Both the ^[and the \e are different ways to encode a escape sequence; a good link to learn about it: [http://jafrog.com/2013/11/23/colors-in-terminal.html](http://jafrog.com/2013/11/23/colors-in-terminal.html) I don't know why filebeat uses a different way to represent the same character than your original console …

---

_[View the full topic](https://discuss.elastic.co/t/after-updating-logstash-to-7-7-from-7-6-regex-isnt-working-the-same/234012)._