# How to monitor Lucene inner ES

**URL:** <https://discuss.elastic.co/t/how-to-monitor-lucene-inner-es/149967>\
**Category:** Elasticsearch\
**Created:** [September 26, 2018, 9:14am UTC](https://discuss.elastic.co/t/how-to-monitor-lucene-inner-es/149967 "2018-09-26T09:14:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![LazyMonster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lazymonster/32/94166_2.png) [@LazyMonster](https://discuss.elastic.co/u/LazyMonster)\
**Post date:** [September 26, 2018, 9:14am UTC](https://discuss.elastic.co/t/how-to-monitor-lucene-inner-es/149967/1 "2018-09-26T09:14:31Z")

</div>

I am working with ES 2.4.1 and ES 6.4.0. When I start ES, I can monitor the process of ES instance using some profiler tools (actually, ES instance is an Java service). I can control the XMX and XMS of ES instance.  
But, in some case, my ES instance was destroy (maybe the reason was Out Of Memory). But I didn't know actually the reason was. The XMX is very smaller than RAM capability. The only reason I concern is how much the memory the Lucene was used.  
Is there any way to monitor Lucene inner ES?

---

<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 24, 2018, 9:21am UTC](https://discuss.elastic.co/t/how-to-monitor-lucene-inner-es/149967/2 "2018-10-24T09:21:48Z")

</div>

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