Having all the logs in a central database is a good start, but it does not allow us to explore them in an easy and user-friendly way. We cannot expect developers to start issuing requests to the ElasticSearch API whenever they want to explore what went wrong. We need a UI that allows us to visualize and filter logs. We need K from the ELK stack.
A note to Windows users
You might experience a problem with volumes not being mapped correctly with Docker Compose. If you may see an Invalid volume specification error, please export the environment variable COMPOSE_CONVERT_WINDOWS_PATHS set to 0:
export COMPOSE_CONVERT_WINDOWS_PATHS=0
Please make sure that the variable is exported every time you run docker-compose or docker stack deploy.
You might experience a problem with volumes not being mapped correctly with Docker Compose. If you may see an Invalid volume specification error, please export the environment variable COMPOSE_CONVERT_WINDOWS_PATHS set to 0:
export COMPOSE_CONVERT_WINDOWS_PATHS=0
Please make sure that the variable is exported every time you run docker-compose or docker stack deploy.
Let's create one more service. This time, it'll be Kibana. Besides the need for this service to communicate with logspout and elasticsearch services, we want to...
