# Per-request REST Logging on ES 2+

**URL:** <https://discuss.elastic.co/t/per-request-rest-logging-on-es-2/61540>\
**Category:** Elasticsearch\
**Created:** [September 26, 2016, 9:40pm UTC](https://discuss.elastic.co/t/per-request-rest-logging-on-es-2/61540 "2016-09-26T21:40:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![diranged](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diranged/32/4065_2.png) [@diranged](https://discuss.elastic.co/u/diranged)\
**Post date:** [September 26, 2016, 9:40pm UTC](https://discuss.elastic.co/t/per-request-rest-logging-on-es-2/61540/1 "2016-09-26T21:40:30Z")

</div>

We'd like to be able to log all REST requests into our ES nodes -- I know that I can turn on the "slow query logging" and set the threshold to 0, but I'd like something more robust than that. Is there a logger somewhere buried in ES that logs out enough data that we can create an Apache-style log line for every web request that comes into the ES cluster?

Historically we've done gotten around this by using something like Nginx/APache in front of ES ... but we don't see the need to do that going forward if we can get it through ES directly. Also with ES/Shield now handling SSL and Auth, I really hate to leverage apache purely as a heavy-weight logger..

---

<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:** [September 27, 2016, 4:54am UTC](https://discuss.elastic.co/t/per-request-rest-logging-on-es-2/61540/2 "2016-09-27T04:54:20Z")

</div>

There's not at the moment, even with Shield.

---

<div class="post-metadata">

**Author:** ![diranged](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diranged/32/4065_2.png) [@diranged](https://discuss.elastic.co/u/diranged)\
**Post date:** [September 28, 2016, 10:17pm UTC](https://discuss.elastic.co/t/per-request-rest-logging-on-es-2/61540/3 "2016-09-28T22:17:43Z")

</div>

Do you know if there is a plan to implement it? A bug we can track or vote on? It seems like it shouldn't be that difficult to add, and with the moving of SSL/Auth into Shield, it seems crazy to have to run Nginx/Apache infront of the service still to get this type of logging.

---

<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:** [September 29, 2016, 12:15am UTC](https://discuss.elastic.co/t/per-request-rest-logging-on-es-2/61540/4 "2016-09-29T00:15:56Z")

</div>

You're always welcome to raise a feature request 😃

---

<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 5, 2017, 10:16pm UTC](https://discuss.elastic.co/t/per-request-rest-logging-on-es-2/61540/5 "2017-07-05T22:16:27Z")

</div>


