# Monitoring: Error 400 Bad Request: Cannot read property 'type' of null **URL:** \ **Category:** Elasticsearch\ **Created:** [June 15, 2017, 6:50am UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509 "2017-06-15T06:50:33Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![kiranilla](https://avatars.discourse-cdn.com/v4/letter/k/8e7dd6/32.png) [@kiranilla](https://discuss.elastic.co/u/kiranilla)\ **Post date:** [June 15, 2017, 6:50am UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509/1 "2017-06-15T06:50:33Z")
After installing the x-pack for ES and Kibana, i have restarted the ES and Kibana. Able to login successfully but when i click on the "Monitoring" link i am getting the following error: `Monitoring: Error 400 Bad Request: Cannot read property 'type' of null` I tried re-installing the X-pack but still the same issue persists. Please find the below screen shot for refrerence \*\*Could you please help me in this issue. \*\* **Thanks in Advance.** ![](https://us1.discourse-cdn.com/elastic/original/3X/a/9/a9a8244fcdbb50b87ba3b553bcc32abeb45db00c.JPG) ![](https://us1.discourse-cdn.com/elastic/original/3X/6/9/69b1a6054a0d2d7ea2c2ab4c629ac1f2e75696af.JPG) ![](https://us1.discourse-cdn.com/elastic/original/3X/f/8/f8f0ac633633193815d41e013c4f5a2d1b6a67fc.JPG) ---
**Author:** ![bohyun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bohyun/32/10087_2.png) [@bohyun](https://discuss.elastic.co/u/bohyun)\ **Post date:** [June 18, 2017, 8:12pm UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509/2 "2017-06-18T20:12:51Z")
Hi @kiranilla From your ES logs, it looks like the monitoring data collection might be failing. Can you check to see if you have any indices starting with `.monitoring-*`? You can use Dev Tools \> Console and run `GET _cat/indices` Thanks, Bohyun ---
**Author:** ![kiranilla](https://avatars.discourse-cdn.com/v4/letter/k/8e7dd6/32.png) [@kiranilla](https://discuss.elastic.co/u/kiranilla)\ **Post date:** [June 21, 2017, 6:24am UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509/3 "2017-06-21T06:24:16Z")
THANKS Bohyun for your help.... Yes i am able to see the .monitoring-\* by using the Dev tools. I will delete those indices and check. ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [June 22, 2017, 9:07pm UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509/4 "2017-06-22T21:07:38Z")
Did deleting the indices resolve the issue? ---
**Author:** ![kiranilla](https://avatars.discourse-cdn.com/v4/letter/k/8e7dd6/32.png) [@kiranilla](https://discuss.elastic.co/u/kiranilla)\ **Post date:** [June 23, 2017, 8:37am UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509/5 "2017-06-23T08:37:54Z")
No.. it did not resolve.. still the issue persist ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [June 26, 2017, 10:01pm UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509/6 "2017-06-26T22:01:17Z")
Do you have any templates that might have patterns which clobber the monitoring data? Try the [http://localhost:9200/\_template/](http://localhost:9200/_template/) API and look for templates with index patterns that possibly match match monitoring indices. ---
**Author:** ![Xavi\_Ametller](https://avatars.discourse-cdn.com/v4/letter/x/b5ac83/32.png) [@Xavi\_Ametller](https://discuss.elastic.co/u/Xavi_Ametller)\ **Post date:** [June 30, 2017, 12:14pm UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509/7 "2017-06-30T12:14:30Z")
Hi, We have found the same problem although our trigger has been different. We were: - changing x-pack license from the trial one to a "normal" free one. - and at the same time we were running a resource intensive queries with aggregations. All of a sudden Kibana monitoring tab started with the bad request error and we have been unable to recover it since then. So far we have: - Checked it and the monitoring indices are there - Checked there were no templates causing collisions - Checked Kibana logs and they seem to be empty - Checked ES logs and nothing representative there We have not tried to delete the monitoring indices to see if it recovered, is it worth trying? We are using ES 5.4.0 and Kibana 5.4.0. Any help will be appreciated. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 28, 2017, 12:14pm UTC](https://discuss.elastic.co/t/monitoring-error-400-bad-request-cannot-read-property-type-of-null/89509/8 "2017-07-28T12:14:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.