# Kibana 6.3 Logstash-\* " .IllegalArgumentException:Trying to retrieve too many docvalue\_fields"? **URL:** \ **Category:** Kibana\ **Created:** [June 12, 2019, 10:40pm UTC](https://discuss.elastic.co/t/kibana-6-3-logstash-illegalargumentexception-trying-to-retrieve-too-many-docvalue-fields/185525 "2019-06-12T22:40:43Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![tiagocosta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tiagocosta/32/40045_2.png) [@tiagocosta](https://discuss.elastic.co/u/tiagocosta)\ **Post date:** [June 15, 2019, 2:12am UTC](https://discuss.elastic.co/t/kibana-6-3-logstash-illegalargumentexception-trying-to-retrieve-too-many-docvalue-fields/185525/3 "2019-06-15T02:12:19Z")
@Asa_Zalles-Milner I think you are right on the cause of the problem and it makes sense to work for `logstash-env-*` and not for `logstash-*`. I think the best thing to do here is a solution already posted on other topic ([Kibana requesting too many doc values](https://discuss.elastic.co/t/kibana-requesting-too-many-doc-values/147760)) that I will also transcript here: > 1. As you suggested, you could try increasing `max_docvalue_fields_search` for each index, though I have concerns this might not scale. If you continue to index documents with new fields then you'll probably bump up against this limit again. > 2. If you don't actually need to query/aggregate on all of those date fields, then maybe you could try mapping them as strings instead. Then they won't be requested as docvalue fields. > 3. You could also be trying to fit too many different types of data into a single index pattern, i.e. your index pattern is too greedy. Would your use case could allow you to define index patterns which match fewer indices, and thus include fewer date fields? Hope that helps, Cheers --- _[View the full topic](https://discuss.elastic.co/t/kibana-6-3-logstash-illegalargumentexception-trying-to-retrieve-too-many-docvalue-fields/185525)._