Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For the installation of ElasticSearch&Kibana we will use Docker-compose (it is more info here). It's better to check that the version of Docker-compose is updated ). It is and it's recommended that you create a folder and place the docker-compose.yaml file in it.

...

Code Block
languagebash
titleStart service
$ docker-compose [-f <file_name>] up -d 
StartingCreating es01 ... done
StartingCreating k01  ... done

The command above starts the background service in the shell (it takes a few seconds to allow processing). We then check that the containers are running using

Code Block
languagebash
titleVerify service
$ docker-compose ps
Name              Command               State                       Ports
----------------------------------------------------------------------------------------------
es01   /bin/tini -- /usr/local/bin/dobi ...   Up      0.0.0.0:92->9200/tcp,:::92->9200/tcp, 9300/tcp
k01    /bin/tini -- /usr/local/bin/dumb-init -bi ...   Up      0.0.0.0:91->5601/tcp,:::91->5601/tcp

or equally with the command

Code Block
languagebash
titleVerify service (alternative method)
$ docker ps | grep elastic
CONTAINER ID   IMAGE                  COMMAND                  CREATED         STATUS   COMMANDPORTS                 CREATED  STATUS  PORTS                        NAMES 
119eb7e8b36a  NAMES
105b1538d0e3  docker.elastic.co/kibana/kibana:7.815.02                ""/bin/tini -- /usr/local/bin/dumb…"  2hl…"   2 minutes ago   Up    2h   0.0.0.0:91->5601/tcp, :::91->5601/tcp             k01
436366264e1ee902ffce0b93   docker.elastic.co/elasticsearch/elasticsearch:7.815.02   "/bin/tini -- /usr/local…l…"   2 2hminutes ago   Up   2h    9300/tcp, 0.0.0.0:92->9200/tcp, :::92->9200/tcp   es01

Finally, we can connect to the address http://<FIP>:<port>. In our case the address, which needs the VPN, is http://131.154.97.128:91. If we can see the Kibana dashboard, it means that the procedure carried out so far is correct (it may take a couple of minutes from startup to service activation). However, we are not yet able to view the logs generated by our cluster. In the next paragraph we will create a connection between the cluster and the newly instanced log collection service.

...