# Elasticsearch request logging

**URL:** <https://discuss.elastic.co/t/elasticsearch-request-logging/1786>\
**Category:** Elasticsearch\
**Created:** [June 2, 2015, 11:46pm UTC](https://discuss.elastic.co/t/elasticsearch-request-logging/1786 "2015-06-02T23:46:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lpoole](https://avatars.discourse-cdn.com/v4/letter/l/d26b3c/32.png) [@lpoole](https://discuss.elastic.co/u/lpoole)\
**Post date:** [June 2, 2015, 11:46pm UTC](https://discuss.elastic.co/t/elasticsearch-request-logging/1786/1 "2015-06-02T23:46:29Z")

</div>

Hey guys,

I know this subject has come up before, however, I wanted to follow up with further discussion.

Is there any way to easily enable logging of all requests sent to Elasticsearch at the beginning of the query call-stack?

Currently, if an expensive query is sent to a node(s), and that query results in OOME, as far as I know, we have no way to audit what queries were in flight when the service failed.

Any suggestions appreciated.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 3, 2015, 12:34am UTC](https://discuss.elastic.co/t/elasticsearch-request-logging/1786/2 "2015-06-03T00:34:49Z")

</div>

Natively, no.

Shield can do this for you as part of its auditing, otherwise you need to proxy it in some other manner.

---

<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:** [July 6, 2017, 12:10am UTC](https://discuss.elastic.co/t/elasticsearch-request-logging/1786/3 "2017-07-06T00:10:04Z")

</div>