Written on the front
This morning, when this has run throughout the Docker-compose built ELK cluster together, and a little not boil live, so fill up in the morning documentation, today on the company's test server to test the good Ferguson.
In this article it is part of the red line, but a start Kibana instance, es-tribe node connected to the cluster Es to complete the connection through it.
See my article to configure the source Git repository https://github.com/hellxz/docker-kibana.git
Port occupancy
Directory name | Container name | Occupied port number |
---|---|---|
docker-kibana | kibana | 5601 |
File Structure
├── docker-compose.yml
└── .env
This may be the least of this ELK cluster configuration, ha ha
File Description
.env
To docker-compose.yml
provide a host Ip es-tribe nodes to be connected
# just for kibana docker-compose.yml
# this host-ip is elasticsearch tribe-node's machine ip.
ES_TRIBE_HOST=10.2.114.110
The pair is docker-compose.yml
we can see .env
in ES_TRIBE_HOST
the node position 9204 the combined exposure es-tribe
version: "3"
services:
kibana:
image: kibana:7.1.0
container_name: kibana
environment:
- ELASTICSEARCH_HOSTS=http://${ES_TRIBE_HOST}:9204 # connect the es-balance node
- I18N_LOCALE=zh-CN #汉化
ports:
- "5601:5601"
network_mode: "host"
Here there is only one directory, do not write a script to start and end the need is not very high.
Instructions for use
- ES es-tribe ensure cluster node host can Ping through
- Ensure es-tribe node is in service state
- Modification
.env
ofES_TRIBE_HOST
the value to the host Ip es-tribe of - Execution
docker-compose up -d
to start the program executiondocker-compose down
to close the program
So far ELK cluster to build a series of articles the end, the end Sahua
This article is the original article, declined to reprint