@@ -45,7 +45,7 @@ You can also choose to run it in background (detached mode):
$ docker-compose up -d
```
Now that the stack is running, you'll want to inject logs in it. The shipped logstash configuration allows you to send content via tcp:
Now that the stack is running, you'll want to inject logs in it. The shipped Logstash configuration allows you to send content via TCP:
```bash
$ nc localhost 5000 < /path/to/logfile.log
...
...
@@ -58,7 +58,7 @@ And then access Kibana UI by hitting [http://localhost:5601](http://localhost:56
Refer to the Elastic documentation for a list of built-in users: [Setting Up User Authentication](https://www.elastic.co/guide/en/x-pack/current/setting-up-authentication.html#built-in-users)
*NOTE*: You'll need to inject data into logstash before being able to configure a logstash index pattern in Kibana. Then all you should have to do is to hit the create button.
*NOTE*: You'll need to inject data into Logstash before being able to configure a Logstash index pattern in Kibana. Then all you should have to do is to hit the create button.
Refer to [Connect Kibana with Elasticsearch](https://www.elastic.co/guide/en/kibana/current/connect-to-elasticsearch.html) for detailed instructions about the index pattern configuration.
...
...
@@ -76,24 +76,43 @@ By default, the stack exposes the following ports:
*NOTE*: Configuration is not dynamically reloaded, you will need to restart the stack after any change in the configuration of a component.
## How can I tune Kibana configuration?
## How can I tune the Kibana configuration?
The Kibana default configuration is stored in `kibana/config/kibana.yml`.
The Kibana container is using the [shipped configuration](https://github.com/elastic/kibana-docker/blob/master/build/kibana/config/kibana.yml).
## How can I tune Logstash configuration?
If you want to override the default configuration, create a file `kibana/config/kibana.yml` and add your configuration in it.
Then, you'll need to map your configuration file inside the container in the `docker-compose.yml` file. Update the kibana service declaration to:
It is also possible to map the entire `config` directory instead of a single file.
## How can I tune the Logstash configuration?
The Logstash container is using the [shipped configuration](https://github.com/elastic/logstash-docker/blob/master/build/logstash/config/logstash.yml).
If you want to override the default configuration, create a file `logstash/config/logstash.conf` and add your configuration in it.
If you want to override the default configuration, create a file `logstash/config/logstash.yml` and add your configuration in it.
Then, you'll need to map your configuration file inside the container in the `docker-compose.yml`. Update the logstash container declaration to:
Then, you'll need to map your configuration file inside the container in the `docker-compose.yml` file. Update the Logstash service declaration to:
In the above example the folder `logstash/config` is mapped onto the container `/usr/share/logstash/config` so you can create more than one file in that folder if you'd like to. However, you must be aware that config files will be read from the directory in alphabetical order, and that Logstash will be expecting a [`log4j2.properties`](https://github.com/elastic/logstash-docker/tree/master/build/logstash/config) file for its own logging.
It is also possible to map the entire `config` directory instead of a single file, however you must be aware that Logstash will be expecting a [`log4j2.properties`](https://github.com/elastic/logstash-docker/tree/master/build/logstash/config) file for its own logging.
## How can I tune Elasticsearch configuration?
## How can I tune the Elasticsearch configuration?
The Elasticsearch configuration is stored in `elasticsearch/config/elasticsearch.yml`.
...
...
@@ -130,11 +149,11 @@ Follow the instructions from the Wiki: [Scaling up Elasticsearch](https://github
# Storage
## How can I store Elasticsearch data?
## How can I persist Elasticsearch data?
The data stored in Elasticsearch will be persisted after container reboot but not after container removal.
In order to persist Elasticsearch data even after removing the Elasticsearch container, you'll have to mount a volume on your Docker host. Update the elasticsearch container declaration to:
In order to persist Elasticsearch data even after removing the Elasticsearch container, you'll have to mount a volume on your Docker host. Update the elasticsearch service declaration to:
