# Monitoring data not found
**URL:** https://discuss.elastic.co/t/monitoring-data-not-found/66206
**Category:** Elasticsearch
**Created:** [November 16, 2016, 6:28am UTC](https://discuss.elastic.co/t/monitoring-data-not-found/66206 "2016-11-16T06:28:08Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@esamudio](https://discuss.elastic.co/u/esamudio)
#### Post date: [November 16, 2016, 6:28am UTC](https://discuss.elastic.co/t/monitoring-data-not-found/66206/1 "2016-11-16T06:28:08Z")
I have a basic, dummy setup of ES (1 master, 4 data nodes), Kibana (on a separate node) and Xpack. All version 5.0.1 with xpack.security.enabled set to false.
I'm able to see a "Monitoring" section on Kibana but it always says "No Monitoring Data Found". I'm clearly missing some basic config but I'm not sure of what it is that I'm doing wrong. I also added
> action.auto\_create\_index: .security,.monitoring\*,.watches,.triggered\_watches,.watcher-history\*
to elasticsearch.yml (defaults for the rest) on all nodes but that didn't do the trick.
kibana.yml is set to all defaults except for xpack.security.enabled and elasticsearch.url (pointing to master).
Any ideas?
---
### Author:  [@esamudio](https://discuss.elastic.co/u/esamudio)
#### Post date: [November 16, 2016, 7:07am UTC](https://discuss.elastic.co/t/monitoring-data-not-found/66206/2 "2016-11-16T07:07:17Z")
After much debugging, realized that the problem was because I had node.ingest set to false. If I'm not interested in the node.ingest feature of ES5 (so I'm not directly using it), is there a downside to having it turned on in terms of efficiency?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 14, 2016, 7:08am UTC](https://discuss.elastic.co/t/monitoring-data-not-found/66206/3 "2016-12-14T07:08:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.