# Using Kibana internal console API

**URL:** <https://discuss.elastic.co/t/using-kibana-internal-console-api/105037>\
**Category:** Kibana\
**Created:** [October 24, 2017, 10:36am UTC](https://discuss.elastic.co/t/using-kibana-internal-console-api/105037 "2017-10-24T10:36:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ashok\_Kumar](https://avatars.discourse-cdn.com/v4/letter/a/ecccb3/32.png) [@Ashok\_Kumar](https://discuss.elastic.co/u/Ashok_Kumar)\
**Post date:** [October 24, 2017, 10:36am UTC](https://discuss.elastic.co/t/using-kibana-internal-console-api/105037/1 "2017-10-24T10:36:11Z")

</div>

I have kibana-(v5.0.1) . I have used the kibana internal console API ([http://server.com/api/console/proxy?uri=\_search](http://server.com/api/console/proxy?uri=_search)) with serach query as param to search for kibana log and processing them.

Recently when i tried to use the same API against (kibana -v5.4.0) which is in another server , I got nginx error .

I have a set of questions here :

1. What I am doing is wrong to get the log using Kibana API ?

2. Why I'm getting this error. Is the newer versions of Kibana developed to block the use of internal API outside/other applications ?

3. Is there any console RestApi to query Kibana log ?

4. Whether the nginx error is due to the server/by kibana itself ?

My overall goal is to query the Kibana from my application . I'm new to these ELK concepts. Please anyone direct me in right path ..

Thanks in Advance.

---

<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:** [October 24, 2017, 5:49pm UTC](https://discuss.elastic.co/t/using-kibana-internal-console-api/105037/2 "2017-10-24T17:49:44Z")

</div>

If you want to query data via the APIs then just go directly to Elasticsearch.

---

<div class="post-metadata">

**Author:** ![Ashok\_Kumar](https://avatars.discourse-cdn.com/v4/letter/a/ecccb3/32.png) [@Ashok\_Kumar](https://discuss.elastic.co/u/Ashok_Kumar)\
**Post date:** [November 2, 2017, 12:22pm UTC](https://discuss.elastic.co/t/using-kibana-internal-console-api/105037/3 "2017-11-02T12:22:53Z")

</div>

Hi.. thanks ..

Yeah thats correct. But I want to query Kibana irrespective of n number of Elastic configured to my Kibana.  
In our case Users will know only about Kibana not the elastic details.  
Is there any other-way we can achieve the same ?

---

<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:** [November 2, 2017, 8:08pm UTC](https://discuss.elastic.co/t/using-kibana-internal-console-api/105037/4 "2017-11-02T20:08:47Z")

</div>

What about using a coordinating node? [https://www.elastic.co/guide/en/elasticsearch/reference/5.6/modules-node.html#coordinating-node](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/modules-node.html#coordinating-node)

---

<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:** [November 30, 2017, 8:09pm UTC](https://discuss.elastic.co/t/using-kibana-internal-console-api/105037/5 "2017-11-30T20:09:11Z")

</div>

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