Coder Social home page Coder Social logo

cars10 / elasticvue Goto Github PK

View Code? Open in Web Editor NEW
1.7K 22.0 135.0 8.46 MB

Elasticsearch gui for the browser

Home Page: https://elasticvue.com

License: MIT License

JavaScript 7.41% HTML 0.08% Vue 42.90% Shell 0.57% Dockerfile 0.09% SCSS 0.33% Rust 0.76% Makefile 0.25% TypeScript 43.96% CSS 3.65%
elasticsearch elasticsearch-browser elasticsearch-gui elasticsearch-frontend

elasticvue's Introduction

elasticvue

Donate Chrome web store Edge extension Firefox addon Docker build

English / 简体中文

Elasticsearch gui for your browser https://elasticvue.com

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries.

Demo

Contents

  1. About
  2. Usage
  3. Browser support
  4. Troubleshooting
  5. Comparing with other frontends
  6. i18n
  7. Contributing

About

Screenshots

Elasticvue is a free and open-source gui for elasticsearch that you can use to manage the data in your cluster. It has full support for elasticsearch versions 8.x and 7.x. Check the FAQ for more details.

Features

  • Cluster overview
  • Index & alias management
  • Shard management
  • Searching and editing documents
  • Rest queries
  • Snapshot & repository management

Usage

You can use elasticvue in several ways:

Desktop App - recommended

Browser extension

Docker

You have to configure your elasticsearch cluster if you want to use elasticvue via docker

Use the existing image:

docker run -p 8080:8080 --name elasticvue -d cars10/elasticvue

When using docker you can provide some default cluster configuration for your users. You can either set an environment variable or provide a config file as a volume. In either case the content should be a json array of your clusters, looking like this:

[
  {
    "name": "dev cluster",
    "uri": "http://localhost:9200"
  },
  {
    "name": "prod cluster",
    "uri": "http://localhost:9501",
    "username": "elastic",
    "password": "foobar"
  }
]

The keys name and uri are required, username and password are optional. If you want to connect with an api key simply use that as the password and omit the username.

Docker with default clusters in environment variable

Example using environment variable ELASTICVUE_CLUSTERS:

docker run -p 8080:8080 -e ELASTICVUE_CLUSTERS='[{"name": "prod cluster", "uri": "http://localhost:9200", "username": "elastic", "password": "elastic"}]' cars10/elasticvue

Docker with default clusters in config file via volume

Example using config file volume to /usr/share/nginx/html/api/default_clusters.json:

echo '[{"name": "prod cluster", "uri": "http://localhost:9200", "username": "elastic", "password": "elastic"}]' > /config.json
docker run -p 8080:8080 -v /config.json:/usr/share/nginx/html/api/default_clusters.json cars10/elasticvue

Your users will be prompted to optionally import these clusters.

Web version

You have to configure your elasticsearch cluster if you want to use elasticvue via docker

Visit https://app.elasticvue.com.

Self-hosted

You have to configure your elasticsearch cluster if you want to use elasticvue via docker

Please check the wiki for more information.

Elasticsearch configuration

You have to enable CORS to allow connection to your elasticsearch cluster if you do not use the desktop app or the browser extensions.

Find your elasticsearch configuration (for example /etc/elasticsearch/elasticsearch.yml) and add the following lines:

# enable CORS
http.cors.enabled: true

# Then set the allowed origins based on how you run elasticvue. Chose only one:
# for docker / running locally
http.cors.allow-origin: "http://localhost:8080"
# online version
http.cors.allow-origin: /https?:\/\/app.elasticvue.com/

# and if your cluster uses authorization you also have to add:
http.cors.allow-headers: X-Requested-With,Content-Type,Content-Length,Authorization

If you use docker to run your elasticsearch cluster you can pass the options via environment variables:

docker run -p 9200:9200 \
           -e "http.cors.enabled=true" \
           -e "http.cors.allow-origin=/.*/" \
           elasticsearch

After configuration restart your cluster and you should be able to connect.

Browser Support

Any current version of Chrome, Firefox and Edge (Chromium) should work without issues. Safari is mostly untested so your mileage may vary.

Troubleshooting

Before opening an issue please try to reset elasticvue to its default settings:

  1. Open the settings
  2. Download a backup of your current elasticvue data
  3. Click Disconnect and reset

This will reset all your saved filters, and you have to reconnect to your cluster. Please open an issue if your problem persists.

Comparing with other frontends

See the Wiki. Comparing to other frontends

i18n

Elasticvue is available in the following languages:

  • english
  • chinese (about 80% translated)

Help wanted

I do not speak chinese and therefore rely on your help to keep the chinese translation up-to-date. Please open a PR if you notice missing/wrong translations in the chinese version.

Adding a new language

If you want to add a new language: translate src/locales/en.json and open a PR.

Contributing

See CONTRIBUTING.md.

License

MIT

elasticvue's People

Contributors

cars10 avatar cengler avatar hchargois avatar itsgoingd avatar joshzcold avatar qiwihui avatar slow-groovin avatar svenehmer avatar xiangtinglee avatar yansq avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

elasticvue's Issues

[BUG] -Empty record in show detail

Description
Id the id of a record contains a forward slash (/) the show window is emtpy, always contains 'null'

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Click on search
  3. Double click on a record with a '/' in the id

Environment (please include the following information):

  • Elasticsearch version: 7.8
  • Operating system: Windows 10
  • Browser + version: Chrome
  • Elasticvue version: 0.23.1
  • How are you running elasticvue? (docker, browser extension, web app): docker

Firefox Addon currently disabled

Mozilla just removed elasticvue on addons.mozilla.org.

I will look into that and solve it ASAP, in the meantime you can build the addon manually or use elasticvue via docker, the hosted version or another browser.

Explanation:

Mozilla disabled elasticvue because the CSP included unsafe-eval. This was needed because the official elasticsearch javascript client makes use of lodashs template function, which uses the Function constructor.
I removed the official elasticsearch javascript client because it is deprecated anyway. This also lead to the removal of the "api browser" page, because most of the functionality was auto generated from the elasticsearch library.

A new version of elasticvue will be available shortly, this should also fix the firefox addon.

Edit: The addon is available again: https://addons.mozilla.org/en-US/firefox/addon/elasticvue/

[FEAT] Add support for hosts with path

Description
My elasticsearch server is behind URL with path like http://example.com/elasticsearch. When I try to use full url with elasticvue the path is removed: https://example.com//_search?format=json&size=1000&q=*&from=0&_source=.

Could you please add support for it?

[FEAT] Simple Proxy backend to avoid setting cors on elasticsearch server

Description
Thanks for the development of this tool. Can you please provide a simple Proxy backend to avoid setting cors on elasticserver. I don't have access to chrome (iPad connected to remote server) and can not allow setting up cors on elasticsearch server.

The feature is similar to..
Does the feature exist in a similar tool (for example kibana)? If so, please:

Additional context
Anything else?

Edge Extension old version

Elasticvue is available in the edge extension store.

Sadly this is an old version because microsoft is giving me a really hard time right now. I have tried to update elasticvue in the edge store about 10 times now, but they always invent a new reason for rejecting it or they do not read for "notes for certification" and just tell me that the extension does not work.

For now i will keep trying but i don't know when a new version of elasticvue will be available for edge.

In the meantime you can always build the extension locally and install it manually.
Alternatively you can install elasticvue from the chrome web store if you enable "Allow extensions from other stores" in the edge settings.

[BUG] - Long numbers being parsed wrong

When displaying long numbers in Elasticvue, it rounds off to the nearest even number.

For example, the number 74897271582524117 gets displayed as 74897271582524116

Steps To Reproduce

  1. Open elasticvue
  2. Load any row that has a long number

Environment

  • Elasticsearch Version : 7.10.2
  • Windows 10
  • Chrome
  • Elasticvue version : 0.33.0
  • How are you running elasticvue : extension

[BUG] - Cannot connect to cluster with special characters in password

Description

  1. It works on single elastic with no x-pack, no username and password.
    Like this: http://10.112.17.82:9201/
  2. It doesn't work on elastic cluster with x-pack, and using correct username and password.
    Like this: http://elastic:[email protected]:9201/
    NOTICE: But It works with chrome extension Elasticsearch Head!

Steps To Reproduce
Anytime

Screenshots
image

Environment
OS: Ubuntu 16.04
Browser: Firefox 70.0.1
Elaticsearch: 6.8.4 (x-pack on)
Elasticvue: 0.16.0
Running Mode: firefox add-ons
Important Elasticsearch Settings:
http.cors.enabled: true
http.cors.allow-origin: "*"
http.cors.allow-headers: X-Requested-With,Content-Type,Content-Length,Authorization
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: certs/elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: certs/elastic-certificates.p12

[BUG] - Sending REST queries with GET leads to an elasticsearch exception

Description
When sending a simple query via a get request, an elasticsearch exception is returned.

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Get to the REST tab
  3. Select the GET method and target the _search endpoint

Screenshots
With GET:
image

With POST
image

Environment (please include the following information):

  • Elasticsearch version: 7.7.0
  • Operating system: MacOS / Docker
  • Browser + version: Chrome Version 83.0.4103.97 (Offizieller Build) (64-Bit)
  • Elasticvue version: 0.22.0
  • How are you running elasticvue? browser extension

Additional context
Anything else?

Yes, thanks a bunch for this awesome project!! After using Head for years and nowadays Kibana instances, this UI is aboslutely awesome to debug queries in a lightweight way!

kibana dev_tools

Description
similar kibana dev_tools

The feature is similar to..
Does the feature exist in a similar tool (for example kibana)? If so, please:

  • /_plugin/kibana/app/kibana#/dev_tools/console
  • don't need open kibana to debug console

Allow mTLS connections to ES

While dismissing the feature request described in Issue #32 as a Bug Report, half the Feature Request was ignored.

TLS

I stupidly thought the -k option on curl would make the request transparent but I should have provided more clarifying info. You’ve offered that there is no way to supply overridden/custom certs in a Chrome, Edge, Firefox extensions. I did some simple research (as a green browser extensions dev) on the topic and I see these extension API features, do these allow supplying custom certs? If feasible, please allow us to supply self-signed certs using these extension features and allow us to connect to ES using self-signed certs.
WebExtensions API - SecurityInfo Chrome Extensions API - certificateProvider

mTLS

See xpack.security.transport.ssl.client_authentication and xpack.security.http.ssl.client_authentication

Does ElasticVue allow mTLS using client certificates? If not please allow us to connect to ES using x509 certs for authentication.

[BUG] - Sorting indices by storage doesn't take units into consideration

Description
On the 'Indices' view sorting by 'Storage' column doesn't take units into consideration, just numbers.

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Click on INDICES in the upper menu
  3. Click on Storage column name to sort

Screenshots
image

Environment (please include the following information):

  • Elasticsearch version: 5.6.10
  • Operating system: centos 7
  • Browser + version: firefox 77.0.1 (64-bit)
  • Elasticvue version: Elasticvue 0.22.0
  • How are you running elasticvue? browser extension

Additional context
n/a

[FEAT] Show aliases in indices overview

Description
I have a cluster with pairs of indices. One in each pair serves as a backup, the other is actively used for searching and indexing. An alias points at the active index.

On the Indices view, it would be helpful to add an alias column (or other indicator) to show which index is currently mapped to an alias.

The feature is similar to..
elasticsearc-head displays a clear indicator with the name of an alias below the index the alias is currently mapped to.

In the image below, bm_se_se is the alias, and it points at the index bm_se_se_2.
image

[FEAT] Add ability to customize search query

Description
The Search page needs another option where the user can set the analyzer for this search. To solve this (and similar needs) the whole search query will be customizable.

Additional context
This feature came up in #37

[BUG] Clicking search result item might open previous opened item.

Description
Clicking search result item might open previous opened item.

Steps To Reproduce
List the steps to reproduce your problem:

  1. Opens https://app.elasticvue.com in browser. (Firefox or Chrome)
  2. Navigates to SEARCH tab and search for '*'
  3. Click the first item then close the popup result dialog.
  4. Click the second item.

Environment (please include the following information):

  • Operating system: macOS
  • Browser + version: Firefox Quantum 66.0.3 (64bit) / Google Chrome Version 73.0.3683.103 (Official Build) (64-bit)
  • Elasticvue version: 0.10.0
  • How are you running elasticvue? (docker, chrome extension, web app): chrome extension & official web app.

Possibility to store urls to many instances of Elasticsearch

Would it be possible to include an option for Chrome Extention to store and switch between different indexes?
It is often that many instances of ElasticSearch are present (for example dev and production) and it would be great if there was an easy way to switch between them.

[BUG] - cannot open documents in elasticsearch 8

Description
Hi Carsten,
suddenly the content of the index is no longer displayed, but that had worked before.

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Click on search -> show

Screenshots
no_index_show

Environment (please include the following information):

  • Elasticsearch version: 8.0
  • Operating system: docker image
  • Browser + version: chrome and firefox latest
  • Elasticvue version: 0.22.0
  • How are you running elasticvue: browser extension

All unit tests fails

All unit tests fails
Yarn serve works well but All unit tests fails

Steps To Reproduce

  1. yarn unit:test =>
yarn run v1.22.4
$ vue-cli-service test:unit
 FAIL  tests/unit/components/shared/BackButton.spec.js
  ● Test suite failed to run

    /home/nb/project/elasticvue/tests/unit/components/shared/BackButton.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import Vuetify from 'vuetify';
                                                                                                    ^^^^^^^

    SyntaxError: Unexpected identifier

      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17)

and so on ...

Test Suites: 15 failed, 15 total
Tests:       0 total
Snapshots:   0 total
Time:        1.343s
Ran all test suites.
error Command failed with exit code 1.

node v10.16.2
@vue/cli 4.2.2

Thank You!

Support SSL certificate

Hi all,
In order to connect to my customer's ES server I need to associate an SSL certificate.
This has been provided via a pfx certificate.
Just to give you an example in Postman this is possible through the Certificates menu:

image

Is it possible to add this feature? This is the only thing which is preventing me from using this fantastic tool! 😊
Thanks in advance!

[BUG] Switching between index pattern and index selection does not work correctly

Description
Switching between index pattern and index selection does not work correctly, the search form always uses the wrong value to search.

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Go to search
  3. Enter an index pattern
  4. Click on "or select indices"
  5. Click on "search"
  6. Now the index pattern is still active and not the empty index selection

Environment (please include the following information):

  • Operating system: Manjaro
  • Browser + version: Chrome 76
  • Elasticvue version: 0.11.0
  • How are you running elasticvue? (docker, chrome extension, web app): Dev

[BUG] - Reletive path

Description
Pathes hardcoded

Steps To Reproduce
I would like to run Elasticvue on site subfolder - https://subdomain.domain.com/elasticvue/

...
    location /elasticvue/ {
        alias /var/www/elasticvue/dist/;
        try_files $uri $uri/ /index.html?$args;
    }
...

And with this configuration many 404 errors when trying to access https://subdomain.domain.com/elasticvue/ cause links from index.html go https://subdomain.domain.com/assets/... and not to https://subdomain.domain.com/elasticvue/assets/...

Screenshots
Not needed.

Environment (please include the following information):

  • Elasticsearch version: current
  • Operating system: centos
  • Browser + version: any
  • Elasticvue version: current
  • How are you running elasticvue? (docker, browser extension, web app): host assets on my own

Update to vuejs 3

Before reaching 1.0 with elasticvue i want to update to vuejs 3 to leverage the composition api.

This is currently blocked by #46

TODO

  • Rewrite all components to use the composition api
  • Update to vuetify 3

[BUG] - Not possbile to run query with _BULK and multiple lines

I am trying to run the following valid lines, but the ´"Run Query" button is not available. The query runs fine with other tools.

POST /cmdb_nodes/_bulk

{ "index" : { "_index" : "cmdb_nodes", "_id" : "xxxx.xxx" } }
{"name": "xxx","system": "zzz","address": "11,4","nodeType": 1,"vendor": "yyy","model": "","manufactored": "1900-01-01T00:00:00","nodePath": "xxxx.xxx","description": "","reference": "","funcLoc": "na","cmdbType": 4,"properties": [],"linkInfo": "","status": 0},

Environment:

  • Elasticsearch version: 7.1
  • Operating system: Windows server 2019
  • Browser + version: Chrome 87.0.4280.66 (Official Build) (64-bit)
  • Elasticvue version: 0.30.0
  • Running elasticvue as a chrome browser extension:

Screenshots
Screenshot_1

[BUG] Missing table headers

Hi, Carsten,

Description
not showing table headers at search menu (/index.html#/search)
In DOM structure they are empty.
Tried "Sticky table header" on and off, no result.

Steps To Reproduce

  1. Open elasticvue
  2. Click search menu
  3. empty :-)

Screenshots
esvue

Environment (please include the following information):

  • ElasticSearch 7
  • Ubuntu 18.04.3 server, client Windows 10 pro
  • on client Google Chrome. 76.0.3809.100 (64 bit)
  • on client Elasticvue 0.11.0
  • on client chrome extension

Additional context
thanks for your work

Please add comparison to cerebro

We have gone through many ES interaction tools, the overall movement was

head -> kopf -> cerebro

Can you compare your tool to cerebro? It's from the same author as kopf. It's very good.

[FEAT] Possibility to hide system indices

Description
Indices that start with "." are considered system indices. Would be nice to have an option to hide them from the view. There could be many of them and it is quite annoying to have it mixed with those that I created.

[BUG] - Cannot change height of request body after switching to horizontal layout

Description
Cannot change height of request body after switching to horizontal layout

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Click Query -> Rest
  3. Select horizontal layout
  4. Try to resize the request body input

Environment (please include the following information):

  • Operating system: Linux
  • Browser + version: Chrome 77
  • Elasticvue version: 0.14.0
  • How are you running elasticvue? (docker, chrome extension, web app): chrome extension

[FEAT] Rename cluster

Description
Once the cluster is connected to, you can't change the name displayed in the top left corner.

Help wanted: Elasticvue needs a new name

Elasticvue needs a new name, because "elastic" is a registered trademark of elastic.

Please comment any ideas that you might have! Just keep in mind that

  • the .com domain should be free
  • the name should not be in use already on the chrome webstore, the firefox webstore or the edge webstore

Thanks!

Ideas so far:

  • searchgui
  • indexgui
  • rubbervue
  • rubberlense
  • strechyvue
  • esvue
  • esgui
  • esblade
  • vuelastic

[BUG] - Not connected

Description
Do not connect to ES. Try to use extansion in FF and Chrome, result the same.

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Click on Test connection
  3. GET request sended, recieve response with status 200 with standard greeting message from ES in body.

Screenshots
ES

Environment (please include the following information):

  • Operating system: Linux Mint 19.2
  • Browser + version: FireFox 72, Chrome 70
  • Elasticvue version: 0.18.0
  • How are you running elasticvue? (docker, chrome extension, web app): firefox and chrome extension

Additional context
using another tools like elasticsearch-head extension work properly.

[BUG] Can't connect to ES 7.1.1

Description
I can't cannot to my ES instance since I upgraded to 7.1.1 from 6.7.1

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Click on TEST CONNECTION
  3. I get
Could not connect. Please make sure that
Your cluster is reachable via https://elastic:[email protected]
You added the correct settings to your elasticserach.yml and restarted your cluster
Either your cluster is not reachable or you did not configure CORS correctly.

Interestingly, when doing right click, inspect, I get 200 OK and the json answer from ES in the network tab:

{
  "name" : "xxx",
  "cluster_name" : "xxx",
  "cluster_uuid" : "xxx",
  "version" : {
    "number" : "7.1.1",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : "7a013de",
    "build_date" : "2019-05-23T14:04:00.380842Z",
    "build_snapshot" : false,
    "lucene_version" : "8.0.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

Of course I already added the necessary config in elasticsearch.yml, and it was working perfectly before the upgrade from 6.7.1.

Environment (please include the following information):

  • Operating system: CentOS7
  • Browser + version: Chrome 75.0.3770.80
  • Elasticvue version: latest docker image
  • How are you running elasticvue? docker

Am I missing anything, or could this be due to the new security features of 7.1.1?

Got 'ERR_TOO_MANY_REDIRECTS' after refreshing extension page

chrome-extension://hkedbapjpblbodpgbajblpnlpenaebaa/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/index.html?route=/

This page isn’t working hkedbapjpblbodpgbajblpnlpenaebaa redirected you too many times.

Try clearing your cookies.

ERR_TOO_MANY_REDIRECTS

[FEAT] CRUD operations while browsing data (Similar to Dejavu)

Description
So far Elasticvue has been my favorite ElasticSearch GUI, however the only feature I am missing which exists in Dejavu is the ability to create fields and update them while browsing.

This is extremely useful when you're going through your data and want to categorize them by filling out the value for another field.

The feature is similar to..

Dejavu supports CRUD operations while browsing the data
https://github.com/appbaseio/dejavu

[FEAT] Upload the chrome addons to microsoft edge extensions store

Description
Upload the chrome addons to microsoft edge extensions store

Additional context
we can not access chrome store in china ,but we can access microsoft store to download edge extension, so please upload this chrome extension to microsoft store or provide the crx file

2021 Survey results

Thank you all for answering the survey!
Before going over the results i want to use this opportunity to talk some numbers.

Stats

Elasticvue can be installed / used in many different ways, and i have usage numbers for at least some of these:

Method Daily users 1y ago Daily users 6m ago Daily users now
Chrome extension ~2500 ~10000 ~16000
Firefox addon ~1000 ~2000 ~2400
Edge extensions - - -
Docker addon - - -
Web app - - -
Self hosted / manual - - -

As you can see, usage numbers for the chrome addon are now more then 6 times higher then one year ago. According to these numbers, i guess that elasticvue has about 20000-25000 daily users overall.

In total, 223 users did answer the survey. This might not seem like a lot, but your answers where extremely helpful!

Survey results

Survey was open from 28.05.2021 to 30.06.2021

Question 1: What is your preferred way of running elasticvue?
As expected most participants use a browser extension for elasticvue, with chrome leading by a big margin.
image

Question 2: For how long have you been using elasticvue?
Most users are using elasticvue for less then a year.
image

Question 3: Did you have issues during elasticvue setup and the connection to your cluster?
The bulk did not have any issues, but about 30% still had some - i will look into ways to improve the setup.
image

Question 4: Which of the following features do you use regularly?
Fortunately it seems that all features of elasticvue are being used.
image

Question 5: Where do you think elasticvue could be improved?
Again, most users agree on this: More then 60% of the participants want more features, with more then 40% thinking that the design could be improved. I agree!
image

Question 6: Do you also use another elasticsearch frontend?
As expected most participants also use kibana for various tasks.
image

Question 7 and 8: If so, what features do you use that are missing in elasticvue? | If you could add a feature to elasticvue, what would it be?
These questions lead to some great feature suggestions. I will include the most common:

Feature Amount Already implemented? Planned Comment
REST/Search query history / templates / examples 23 No Yes Planned for the next release (0.36.0)
CRUD Documents 14 No Yes Planned for the version after the above
Structured query builder (es-head/mirage) 7 No No I am not sure if this is the right way to go. I would prever a better (and context-sensitive) typeahead instead of a gui.
Index settings / mappings 3 No Yes Planned
Shard display/visualization + relocation 3 No No Unsure
Standalone / Desktop client 5 No No Right now elasticvue is distributed in 6 different ways and this already feels a bit too much. Also, a standalone client would have to be a heavy electron app and i am not really a fan of that, because there is exactly zero benefit of using this instead of a browser addon.
REST/Search JSON export 5 No Yes Coming in one of the next versions
Aggs, Diagrams, Analyzers 4 No No Really complex topic, so far i don't plan to implement analyzers/aggs/diagrams in elasticvue
Typeahead 4 Yes Should be context-sensitive. Planned
Search interface: more filters 2 No No Does not really make sense. If you want more filters then you simply have to adjust the query
REST Split view 1 Yes Already implemented months ago
Search with profiles 1 No Maybe Unsure about how exactly this would look like. I think you should probably use the REST interface for this
Ingest pipeline management 1 No No
Search pagination link to first page 1 Yes Implemented in 0.35.0
Realtime view 1 Kinda Yes Most views in elasticvue offer a way to auto-reload in a certain interval. This is missing on the search page and will be added.
ILM 1 No No
Search column selection: "unselect all" button 1 Yes Implemented in 0.35.0
Purge data via elasticvue 1 Yes Already implemented months ago. You can delete indices and purge the whole cluster (in utilities). Deleting single docs is still missing.
KQL support 1 No Maybe I like the idea, but it's a huge amount of work.

elasticvue_survey_2021.csv

Overall many users are simply missing all the features that kibana has. Elasticvue does not want to be a clone of kibana. Personally i see elasticvue as a tool for daily tasks like searching, inspecting and, to some extend, common management tasks. Complex (and in my experience, rarely used/changed) things like ILM, Ingest Pipeline management, Shard reloaction etc might be out of the scope. Feel free to discuss this here.

I have also noticed that many features where requested that elasticvue already has, so i might have to advertise them better.

Apart from that, there were many great suggestions in your answers. I have already fixed some of these in 0.35.0:

  • Reworks saved cluster selection to table (with pagination and filter) to improve support for users with 10+ clusters
    image

  • Can open documents in new tab by using ctrl+click. Standalone click will still open document in modal. Please
    report if this does not work on macOS.

  • Adds icons for first/last page in all tables

  • Adds "uncheck" button to deselect all columns in search table

  • Adds additional hint to set http.cors.allow-headers when adding a cluster that uses authorization

Future

For now i will work on implementing the suggested features and improvements for elasticvue. Hopefully we can release 1.0 this year once vuetify has full support for vuejs 3.0. This will also include an updated design.


🎉 Thanks for using elasticvue 🎉

[BUG] - Closed index will cause INDICES table blank

Description
Closed index will cause INDICES table blank.
The browser console
TypeError: Expected a finite number, got number: NaN

Steps To Reproduce
List the steps to reproduce your problem:

  1. Open elasticvue
  2. Click on INDICES tab
  3. Select one index and click Close Index
  4. Refresh page(Refresh button cannot reproduce)
  5. Indices table will be blank

Screenshots
Browser Console error
Actual indices XHR response

Environment (please include the following information):

  • Elasticsearch version: 7.4.2
  • Operating system: MacOS 10.12
  • Browser + version: Firefox 77.0.1
  • Elasticvue version: Elasticvue 0.23.0
  • How are you running elasticvue? (docker, browser extension, web app): Firefox extension.

Additional context
When an Index is closed, it's store.size will be null.
I think we should check if value is NaN here

[FEAT] Use elasticsearch sort functionality

Description
It would be nice if the solution could use the "Multi Search API (_msearch)" instead of just _search. In the way sorting and more could be done by elastic.
https://www.elastic.co/guide/en/elasticsearch/reference/current/search-multi-search.html#search-multi-search

As it is now, you could potentially hide records/information from the user, if you have more than the default 1000 records that's fetched.
Let's say there are 1500 records in ES. The 1000 records are fetched to the frontend, and the user sorts on a date field in descending order. Because only the first 1000 records are fetched, the #1000 record are at the top now and not #1500 as I would expect.

The feature is similar to..
Dejavu uses _msearch
https://github.com/appbaseio/dejavu

Allow TLS connections to ES

Description
Please build support for TLS and mTLS connections to ES.

Currently https connections to ES result in:

image

$ curl -ks https://localhost:9202
{
  "name" : "my-cluster.default.svc.cluster.local",
  "cluster_name" : "my-cluster",
  "cluster_uuid" : "J_ABE80yTBmd7jeH_9qpGw",
  "version" : {
    "number" : "7.0.1",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : "e4efcb5",
    "build_date" : "2019-04-29T12:56:03.145736Z",
    "build_snapshot" : false,
    "lucene_version" : "8.0.0",
    "minimum_wire_compatibility_version" : "6.7.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

Incorrect documents count when mapping is of nested type

Description
When documents have nested objects within them, the overall count of the documents in an index is reported inaccurately.

Steps To Reproduce
List the steps to reproduce your problem:
Make sure to have an index with few records that have nested objects within it. ("type" : "nested")

  1. Open elasticvue
  2. Click on INDICES
  3. Check the count of documents
  4. Using Elasticsearch's /_count API, check the number of documents in the index, it'll be different.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.