...
For the installation of ElasticSearch and Kibana we will use Docker-Compose (it is better to check that the version of Docker-Compose is updated). It is recommended that you create a folder and place the docker-compose.yml
file in it.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
version: '3.3' services: es01: image: docker.elastic.co/elasticsearch/elasticsearch:7.9.0 # <--- get the latest version container_name: es01 environment: - node.name=es01 - cluster.name=es-docker-cluster - discovery.type=single-node - bootstrap.memory_lock=true - "ES_JAVA_OPTS=-Xms512m -Xmx512m" ulimits: memlock: soft: -1 hard: -1 volumes: - data01:/usr/share/elasticsearch/data ports: - 92:9200 # <--- change host port. Here we used 92 networks: - elastic k01: container_name: k01 image: docker.elastic.co/kibana/kibana:7.9.0 # <--- get the latest version environment: SERVER_NAME: kibana ELASTICSEARCH_HOSTS: http://es01:9200 ports: - 91:5601 # <--- change host port. Here we used 91 networks: - elastic volumes: data01: driver: local networks: elastic: driver: bridge |
Open the ports indicated in the file on OpenStack and then launch, inside the folder just created, the command (if the file name is different from docker-compose.yml
, then specify it after the "-f
" option)
Code Block | ||||
---|---|---|---|---|
| ||||
$ docker-compose [-f <file_name>] up -d Starting es01 ... done Starting k01 ... done |
...
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.
...
Remember to run the docker-compose command inside the folder where the .yaml
file is located.
Log deployment with FileBeat
...