# How to See Kibana Requests to ES

**URL:** <https://discuss.elastic.co/t/how-to-see-kibana-requests-to-es/55351>\
**Category:** Kibana\
**Created:** [July 12, 2016, 8:38pm UTC](https://discuss.elastic.co/t/how-to-see-kibana-requests-to-es/55351 "2016-07-12T20:38:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mitchswaldman](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@mitchswaldman](https://discuss.elastic.co/u/mitchswaldman)\
**Post date:** [July 12, 2016, 8:38pm UTC](https://discuss.elastic.co/t/how-to-see-kibana-requests-to-es/55351/1 "2016-07-12T20:38:43Z")

</div>

Hello!

Is there a way to see the requests that Kibana makes to ES to check if a plugin is installed? I'm currently having issues with Kibana saying that the x-pack plugin is not installed on my ES cluster. I've found in the Kibana code where the call to the ES client is made, but now I'd like to actually see that call. From what I can tell, the call should not be returning a 400 error response, but it is. I'd very much like to see the exact call that's being made. Is that at all possible to see? Thanks for your time!

Cheers,  
Mitch

---

<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:** [July 13, 2016, 4:31am UTC](https://discuss.elastic.co/t/how-to-see-kibana-requests-to-es/55351/2 "2016-07-13T04:31:14Z")

</div>

You can try with your browsers developer tools.

---

<div class="post-metadata">

**Author:** ![mitchswaldman](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@mitchswaldman](https://discuss.elastic.co/u/mitchswaldman)\
**Post date:** [July 13, 2016, 4:37pm UTC](https://discuss.elastic.co/t/how-to-see-kibana-requests-to-es/55351/3 "2016-07-13T16:37:40Z")

</div>

Unfortunately the developer tools only show the calls from the Kibana dashboard to the Kibana server. I really would like to see the calls from the Kibana server to the Elasticsearch server.

---

<div class="post-metadata">

**Author:** ![tinle](https://avatars.discourse-cdn.com/v4/letter/t/c77e96/32.png) [@tinle](https://discuss.elastic.co/u/tinle)\
**Post date:** [July 13, 2016, 4:56pm UTC](https://discuss.elastic.co/t/how-to-see-kibana-requests-to-es/55351/4 "2016-07-13T16:56:55Z")

</div>

Insert a proxy between Kibana and Elasticsearch.

In your kibana.yml, change the line:

`elasticsearch_url: "http://localhost:9200"`

to point to a proxy that logs everything going through it. The proxy could be anything, squid, nginx, haproxy or even nc.

Tin

---

<div class="post-metadata">

**Author:** ![mitchswaldman](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@mitchswaldman](https://discuss.elastic.co/u/mitchswaldman)\
**Post date:** [July 13, 2016, 6:44pm UTC](https://discuss.elastic.co/t/how-to-see-kibana-requests-to-es/55351/5 "2016-07-13T18:44:49Z")

</div>

The ES url was already being redirected to an AWS elastic load balancer, and I followed your advice and logged all the requests going through the load balancer. I cannot find the word "\_xpack" within the logged request URLs at all. It seems like kibana isn't making that call, which is really throwing me.

---

<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, 1:46pm UTC](https://discuss.elastic.co/t/how-to-see-kibana-requests-to-es/55351/6 "2017-07-06T13:46:54Z")

</div>


