# \[solved\] Kibana Monitoring \[illegal\_argument\_exception\]
**URL:** https://discuss.elastic.co/t/solved-kibana-monitoring-illegal-argument-exception/187974
**Category:** Kibana
**Tags:** elastic-stack-monitoring
**Created:** [June 28, 2019, 5:32am UTC](https://discuss.elastic.co/t/solved-kibana-monitoring-illegal-argument-exception/187974 "2019-06-28T05:32:57Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@rog\_NB](https://discuss.elastic.co/u/rog_NB)
#### Post date: [June 28, 2019, 5:32am UTC](https://discuss.elastic.co/t/solved-kibana-monitoring-illegal-argument-exception/187974/1 "2019-06-28T05:32:58Z")
I'm on my Lab to update from 6.6.1 to 7.2
After all work done, I had on the tab _Monitoring_ this error on the lower right corner of the browser:
> Monitoring Request Error
> [illegal\_argument\_exception]
> Fielddata is disabled on text fields by default. Set fielddata=true on [event.dataset] in order to load fielddata in memory by uninverting the inverted index.Note that this can however use significant memory. Alternatively use a keyword field instead.: Check the Elasticsearch Monitoring cluster network connection or the load level of the nodes.
> HTTP 503
I've then done a search for this [event.dataset] under _Management-\>Kibana, index patterns_.
On each pattern I've entered this _ **event.dataset** _ until I've found it. In my case it was in **filebeat-**
In _Management -\> Elasticsearch, Index Management_ I've entered _ **filebeat-** _ and saw (for my luck) only one index.
In the Dev tools:
```
PUT filebeat-[something]/_mapping
{
"properties": {
"event.dataset": {
"type": "text",
"fielddata": true
}
}
}
```
This did the right stuff, to remove [illegal\_argument\_exception]
Hopefully there are someone out there, which could help my finding.
cheers
---
### Author:  [@markov00](https://discuss.elastic.co/u/markov00)
#### Post date: [July 25, 2019, 10:55am UTC](https://discuss.elastic.co/t/solved-kibana-monitoring-illegal-argument-exception/187974/2 "2019-07-25T10:55:40Z")