tradiff / elasticsearch-head-chrome Goto Github PK

while my es service is config with httpbasic auth,
but i want use this to view my cluster instance info.
where can config the auth??

When using the chrome extension on an elastic 6.0.0 cluster every search fails with a:

{
"error": "Content-Type header [application/x-www-form-urlencoded] is not supported",
"status": 406
}

Works on old elastic versions.

Is there a way to connect using API Key: https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-create-api-key.html

JS client can connect like this:
https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/7.x/client-connecting.html#auth-apikey

Dear:

if my elasticsearch open username/password, how to access elasticsearch via elasticsearch-head-chrome? i can't find any setting to input username/password.

My Elasticsearch instance is secured with basic authentication. Is there an option to enable this in the Chrome extension? I could not find it immediately.

After upgrading the ES Cluster to ES 6.8.3, the elasticsearch-head extension (Version 0.1.5) doesn't work anymore when status of cluster is yellow. The browserconsole shows the following error:

Uncaught TypeError: Cannot read property 'size_in_bytes' of undefined
at Class._indexHeader_template (app.js:3288)
at Array.map ()
at Class._main_template (app.js:3337)
at Class.init (app.js:3070)
at Class.prototype.(anonymous function) [as init] (chrome-extension://ffmkiejjmecolpfloofpjologoblkegm/elasticsearch-head/app.js:281:64)
at new Class (app.js:265)
at Class._drawNodesView (app.js:3623)
at Class.draw_handler (app.js:3618)
at app.js:351
at Array.forEach ()

I'm trying to perform a simple search on my index, but the result is never shown and the "Requesting..." message never leaves. This was my first attempt to run the plugin and all my indices are listed with the correct amount of documents indexed.
I'm using:
Chrome Version 59.0.3071.115
Elasticsearch 2.4.0

A while ago I turned on https and added basic auth, after which this extension worked for a while, but then stopped working.

Inspection of the network requests shows 403 errors on the following endpoints...

• /_stats fails with the error message "current license is non-compliant for [security]"
• /_nodes/stats fails with the same error
• /_cluster/health fails with the same error

Are these endpoints necessary for this extension to work, or could it work (at least minimally) without them?

I am using an AWS Elastic Search Service, which i have 2 masters and 6 data nodes. In the Extension 1 of my Masters shows as a Data Node with the Circle icon instead of a star icon.

i have confirmed by viewing node stats that it has the role of "master" and not "data". See attached screenshots

Does this extension supports Open Distro ? , I am not able to get status and connectivity with Open Distro.

I use the Chrome Extension and it would be nice to see an option for User Settable List of Endpoints to connect to populated in a Dropdown (SELECT->OPTION) List for the Connect Box instead of the INPUT box, for fast switching between Clusters/Endpoints.

The Image shows an example of what I mean. I was able to do it using DevTools in Chrome to modify it for that moment. THe Submit still works, but the SELECT will change back to INPUT once it loads the new cluster selected.

Give option in the Plugin Settings to set Endpoint Name and Endpoint URL to be added in as

<select class="uiClusterConnect-uri" name="cluster">
  <option value="https://prodcluster.example.com">ES-Prod</option>
  <option value="https://testcluster.example.com">ES-Test</option>
  <option value="http://kibana-test.example.com:9200">Kibana-Test</option>
</select>

Same Feature Request as I reported for the main elastic search head application:
Change Connect Input Box to User Settable list of ElasticSearch Endpoints #379

In query tab, any ES query failed to perform. The error is "Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'sha256-Rpn+rjJuXCjZBPOPhhVloRXuzAUBRnAas+6gKVDohs0='"."

In browser debug mode, the query request and response actually returned. But the query result could not be shown in result zone due to Chrome CSP.

in "Any Request" tab in "Query" section:
query's body: {"query":{"bool":{"must":[{"prefix":{"id.keyword":"123"}}]}}}
path: _search
method: POST

How to delete from ES the data which are in the result of the query/request above?

The history panel is great however it can get quite cluttered. Might be a nice feature to be able to manage those items and clear out the ones that are not re-used.

I am not able to use this es-head extension after x-pack installation in es-v6.2.4
Could you please help?

When I do a query on any field must missing, this is the query getting formed. which is ok but

If I query on the field must not missing this wrong query getting generated.

_forcemerge has changed in 6.4.0 - REST API: Reject forcemerge requests with a body elastic/elasticsearch#30792 (issue: elastic/elasticsearch#29584)

I use Elasticsearch 6.5.1. I try to manually run _forcemerge command on a specified index.

In that case, I go to Any Request tab, put test/_forcemerge?max_num_segments=1 in path field, select POST method, remove whole request body. After I press Request button I see Error 400 with message forcemerge takes arguments in query parameters, not in the request body.

The problem is _forcemerge does not allow to send a request body. Currentl,y empty body of request is replaced with empty JSON object {}), it must be empty!

Please check _forcemerge with curl requests.

Send empty JSON object instead of empty body - error

$ curl -H "Content-Type: application/json" -XPOST "http://192.168.1.27:9200/test/_forcemerge?max_num_segments=1" -d "{}"
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"forcemerge takes arguments in query parameters, not in the request body"}],"type":"illegal_argument_exception","reason":"forcemerge takes arguments in query parameters, not in the request body"},"status":400}

Send empty request body - everything is OK

$ curl -H "Content-Type: application/json" -XPOST "http://192.168.1.27:9200/test/_forcemerge?max_num_segments=1" -d ""
{"_shards":{"total":10,"successful":5,"failed":0}}

In my opinion to send empty request body should be checkbox Empty body next to Pretty. When Empty body is selected textarea form should be disabled.

Can you please merge this commit: 02ebf12
Because of this issue: Fail to sort nodes by address when there are unassigned shards

Hello there,

I'm just writing to let you know that it appears as though this extension was removed from the Chrome Web Store.

Curious if you had any thoughts/comments on why that might have happened.

Thanks!

The request for _analyze is send like this
http://localhost:9200/ik-demo/_analyze?text=***

but, I got response code 400
{"error":{"root_cause":[{"type":"parse_exception","reason":"request body or source parameter is required"}],"type":"parse_exception","reason":"request body or source parameter is required"},"status":400}

i can't find it

It didn't refresh the list of indices for both "Browser" & "Structured Query" tab, after removal some indices.

There's no error found in console log.

Look like head not work with ES 7.*

Hi, im new in elasticsearch so im just trying to understand from the beggining.

Recently i start using the elasticsearch -head, but im not understanding how it works, i mean if i want to create some document, i can do it in both? from the "structured query"and the "any request" tabs?

Hello team,

since enabling SAML for kibana, ES head is not working with 401 error.

is this expected behavior ?

There is no problem to enter kibana page using SSO authentication since SAML enablement.

Thanks,
BmW.

My ES 7.0.1 clusters each use a self-signed TLS cert to serve client requests.

$ curl -ks https://localhost:9202/_cluster/health?pretty
{
  "cluster_name" : "transcriptions-cluster1",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 5,
  "number_of_data_nodes" : 5,
  "active_primary_shards" : 100,
  "active_shards" : 200,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 100.0
}

I am unable to connect to these clusters using the head plugin.

Can I get the head module tolerate "Insecure"/aka self-signed server certificates?