From dcf76589724788e46636343a5fc1f351931971dd Mon Sep 17 00:00:00 2001 From: simon Date: Fri, 22 Jul 2022 18:26:12 +0700 Subject: [PATCH] add kibana quick start guide --- CONTRIBUTING.md | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 517f22ef..e73df9db 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -30,7 +30,25 @@ This is my setup I have landed on, YMMV: - This `deploy.sh` script is not meant to be universally usable for every possible environment but could serve as an idea on how to automatically rebuild containers to test changes - customize to your liking. ## Working with Elasticsearch -Additionally to the required services as listed in the example docker-compose file, the **Dev Tools** of [Kibana](https://www.elastic.co/guide/en/kibana/current/docker.html) are invaluable for running and testing Elasticsearch queries. +Additionally to the required services as listed in the example docker-compose file, the **Dev Tools** of [Kibana](https://www.elastic.co/guide/en/kibana/current/docker.html) are invaluable for running and testing Elasticsearch queries. + +**Quick start** +Generate your access token in Elasitcsearch: +```bash +bin/elasticsearch-service-tokens create elastic/kibana kibana +``` + +Example docker compose, use same version as for Elasticsearch: +```yml +kibana: + image: docker.elastic.co/kibana/kibana:0.0.0 + container_name: kibana + environment: + - "ELASTICSEARCH_HOSTS=http://archivist-es:9200" + - "ELASTICSEARCH_SERVICEACCOUNTTOKEN=" + ports: + - "5601:5601" +``` If you want to run queries on the Elasticsearch container directly from your host with for example `curl` or something like *postman*, you might want to **publish** the port 9200 instead of just **exposing** it.