Inspect Button in Kibana 5.0.2


(Ravi) #1

Hi I'm trying to find Inspect button in kibana 5.0.2 as we can see kibana 3.1.2 has flexibility to select
to see api request url is it possible in new kibana 5.0.2 ?

curl -XGET '//localhost:9200/__es/logstash-2016.12.09,logstash-2016.12.08/_search?pretty' -d '{
"facets": {
"terms": {
"terms": {
"field": "site",
"size": 50,
"order": "count",
"exclude": []
},
"facet_filter": {
"fquery": {
"query": {
"filtered": {
"query": {
"bool": {
"should": [
{
"query_string": {
"query": ""LOCAL) Stream failure due to long underflow""
}
}
]
}
},
"filter": {
"bool": {
"must": [
{
"range": {
"@timestamp": {
"from": 1481227319962,
"to": 1481313719962
}
}
}
]
}
}
}
}
}
}
}
},
"size": 0
}'


(Shaunak Kashyap) #2

Yes, look for a button like this in the Kibana UI:

When you click it, you will get tabs like "Request", "Response", etc.


(Ravi) #3

Thanks for reply but Still not able to find the curl -XGET '//localhost:9200/__es/logstash-2016.12.09,logstash-2016.12.08/_search?pretty' -d '{

The one in Kibana 5.0.2 is

Elasticsearch request body
{
"query": {
"bool": {
"must": [
{
"query_string": {
"query": "*",
"analyze_wildcard": true
}
},
{
"range": {
"@timestamp": {
"gte": 1481646834165,
"lte": 1481648634165,
"format": "epoch_millis"
}
}
}
],
"must_not": []
}
},
"size": 0,
"aggs": {
"2": {
"date_histogram": {
"field": "@timestamp",
"interval": "30s",
"time_zone": "America/New_York",
"min_doc_count": 1
}
}
}
}


(Shaunak Kashyap) #4

The Kibana 4 architecture is a bit different from Kibana 3. In Kibana 3 the requests went from the browser directly to your Elasticsearch cluster (that's why you are seeing the http://localhost:9200 in the API request URL from Kibana 3). Kibana 4 has a server component as well so the Kibana UI in the browser makes its request to that server component. It, in turn, makes the appropriate requests to your Elasticsearch cluster.

If you are using Chrome or Firefox, you can open the Developer Tools console and look at network requests. You should see requests that contain /elasticsearch/ in the URL. These requests are ultimately proxied to the Elasticsearch cluster by the Kibana server. So you can grab their bodies and the URL path after /elasticsearch/ and form a request directly against your Elasticsearch cluster.


(Ravi) #5

Thanks Shaunak figured out your explanation is very helpful.

curl -XGET '10.251.33.130:9200/logstash-*/_search?pretty' -d '


(system) #6

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