# Using existing logstash index pattern in Kibana produces 413 Response Error

**URL:** <https://discuss.elastic.co/t/using-existing-logstash-index-pattern-in-kibana-produces-413-response-error/198779>\
**Category:** Logstash\
**Created:** [September 9, 2019, 8:07pm UTC](https://discuss.elastic.co/t/using-existing-logstash-index-pattern-in-kibana-produces-413-response-error/198779 "2019-09-09T20:07:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![swnbdy](https://avatars.discourse-cdn.com/v4/letter/s/aeb1de/32.png) [@swnbdy](https://discuss.elastic.co/u/swnbdy)\
**Post date:** [September 9, 2019, 8:07pm UTC](https://discuss.elastic.co/t/using-existing-logstash-index-pattern-in-kibana-produces-413-response-error/198779/1 "2019-09-09T20:07:22Z")

</div>

Hello team,

Newbie here.

Today I refreshed my index pattern to bring in new fields. After noticing that I had gone from having 18 fields to 2000+ I felt something wasn't as I only expected \>10 fields.

Thinking I was removing some of the unknown fields, I ended up removing the index pattern from Kibana.

Now, when I try to add the logstash-\* index back to Kibana, I get a 413 response error.

From my research I get the idea that it may be from the number of fields coming in the index but I am unsure and quite stuck.

Any help would be very greateful.

Thanks in advance!

---

<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 7, 2019, 8:07pm UTC](https://discuss.elastic.co/t/using-existing-logstash-index-pattern-in-kibana-produces-413-response-error/198779/2 "2019-10-07T20:07:28Z")

</div>

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