# Combined grok pattern for customized logs

**URL:** <https://discuss.elastic.co/t/combined-grok-pattern-for-customized-logs/338535>\
**Category:** Logstash\
**Created:** [July 17, 2023, 10:30am UTC](https://discuss.elastic.co/t/combined-grok-pattern-for-customized-logs/338535 "2023-07-17T10:30:14Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [July 19, 2023, 2:48am UTC](https://discuss.elastic.co/t/combined-grok-pattern-for-customized-logs/338535/10 "2023-07-19T02:48:42Z")

</div>

[This thread](https://discuss.elastic.co/t/getting-illegal-state-exception-error-while-pushing-logs-to-elasticsearch/290029/2) expands upon the problem.

You cannot change the type of a field in an existing index without re-indexing. And all the events need to be consistent about what type a field is.

---

_[View the full topic](https://discuss.elastic.co/t/combined-grok-pattern-for-customized-logs/338535)._