[](https://gitter.im/deviantony/docker-elk?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
Run the latest version of the ELK (Elasticsearch, Logstash, Kibana) stack with Docker and Docker-compose.
Run the latest version of the ELK (Elasticsearch, Logstash, Kibana) stack with Docker and Docker Compose.
It will give you the ability to analyze any data set by using the searching/aggregation capabilities of Elasticsearch and the visualization power of Kibana.
It will give you the ability to analyze any data set by using the searching/aggregation capabilities of Elasticsearch
*[How can I tune the Kibana configuration?](#how-can-i-tune-the-kibana-configuration)
*[How can I tune the Logstash configuration?](#how-can-i-tune-the-logstash-configuration)
*[How can I tune the Elasticsearch configuration?](#how-can-i-tune-the-elasticsearch-configuration)
*[How can I scale out the Elasticsearch cluster?](#how-can-i-scale-up-the-elasticsearch-cluster)
4.[Storage](#storage)
*[How can I persist Elasticsearch data?](#how-can-i-persist-elasticsearch-data)
5.[Extensibility](#extensibility)
*[How can I add plugins?](#how-can-i-add-plugins)
*[How can I enable the provided extensions?](#how-can-i-enable-the-provided-extensions)
6.[JVM tuning](#jvm-tuning)
*[How can I specify the amount of memory used by a service?](#how-can-i-specify-the-amount-of-memory-used-by-a-service)
*[How can I enable a remote JMX connection to a service?](#how-can-i-enable-a-remote-jmx-connection-to-a-service)
## Requirements
### Host setup
1. Install [Docker](https://www.docker.com/community-edition#/download) version **1.10.0+**
2. Install [Docker Compose](https://docs.docker.com/compose/install/) version **1.6.0+**
3. Clone this repository
## SELinux
### SELinux
On distributions which have SELinux enabled out-of-the-box you will need to either re-context the files or set SELinux into Permissive mode in order for docker-elk to start properly.
For example on Redhat and CentOS, the following will apply the proper context:
On distributions which have SELinux enabled out-of-the-box you will need to either re-context the files or set SELinux
into Permissive mode in order for docker-elk to start properly. For example on Redhat and CentOS, the following will
@@ -49,45 +75,81 @@ 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:
Give Elasticsearch about a minute to initialize, then access the Kibana web UI by hitting
[http://localhost:5601](http://localhost:5601) with a web browser.
By default, the stack exposes the following ports:
* 5000: Logstash TCP input.
* 9200: Elasticsearch HTTP
* 9300: Elasticsearch TCP transport
* 5601: Kibana
**WARNING**: If you're using `boot2docker`, you must access it via the `boot2docker` IP address instead of `localhost`.
**WARNING**: If you're using *Docker Toolbox*, you must access it via the `docker-machine` IP address instead of
`localhost`.
Now that the stack is running, you will want to inject some log entries. The shipped Logstash configuration allows you
to send content via TCP:
```bash
$ nc localhost 5000 < /path/to/logfile.log
```
And then access Kibana UI by hitting [http://localhost:5601](http://localhost:5601) with a web browser.
## Initial setup
*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.
### Default Kibana index pattern creation
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.
When Kibana launches for the first time, it is not configured with any index pattern.
By default, the stack exposes the following ports:
* 5000: Logstash TCP input.
* 9200: Elasticsearch HTTP
* 9300: Elasticsearch TCP transport
* 5601: Kibana
#### Via the Kibana web UI
**NOTE**: You need to inject data into Logstash before being able to configure a Logstash index pattern via the Kibana web
UI. Then all you have to do is 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.
*WARNING*: If you're using *boot2docker*, you must access it via the *boot2docker* IP address instead of *localhost*.
#### On the command line
*WARNING*: If you're using *Docker Toolbox*, you must access it via the *docker-machine* IP address instead of *localhost*.
Run this command to create a Logstash index pattern:
*NOTE*: Configuration is not dynamically reloaded, you will need to restart the stack after any change in the configuration of a component.
**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 the Kibana configuration?
### How can I tune the Kibana configuration?
The Kibana default configuration is stored in `kibana/config/kibana.yml`.
It is also possible to map the entire `config` directory instead of a single file.
## How can I tune the Logstash configuration?
### How can I tune the Logstash configuration?
The Logstash configuration is stored in `logstash/config/logstash.yml`.
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.
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 the Elasticsearch configuration?
### How can I tune the Elasticsearch configuration?
The Elasticsearch configuration is stored in `elasticsearch/config/elasticsearch.yml`.
...
...
@@ -95,106 +157,93 @@ You can also specify the options you want to override directly via environment v
```yml
elasticsearch:
build:elasticsearch/
ports:
-"9200:9200"
-"9300:9300"
environment:
ES_JAVA_OPTS:"-Xmx256m-Xms256m"
network.host:"_non_loopback_"
cluster.name:"my-cluster"
networks:
-elk
```
## How can I scale up the Elasticsearch cluster?
### How can I scale out the Elasticsearch cluster?
Follow the instructions from the Wiki: [Scaling up Elasticsearch](https://github.com/deviantony/docker-elk/wiki/Elasticsearch-cluster)
Follow the instructions from the Wiki: [Scaling out
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 service 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:
```yml
elasticsearch:
build:elasticsearch/
ports:
-"9200:9200"
-"9300:9300"
environment:
ES_JAVA_OPTS:"-Xmx256m-Xms256m"
network.host:"_non_loopback_"
cluster.name:"my-cluster"
networks:
-elk
volumes:
-/path/to/storage:/usr/share/elasticsearch/data
```
This will store Elasticsearch data inside `/path/to/storage`.
# Extensibility
## Extensibility
## How can I add plugins?
### How can I add plugins?
To add plugins to any ELK component you have to:
1. Add a `RUN` statement to the corresponding `Dockerfile` (eg. `RUN logstash-plugin install logstash-filter-json`)
2. Add the associated plugin code configuration to the service configuration (eg. Logstash input/output)
# JVM tuning
### How can I enable the provided extensions?
A few extensions are available inside the [`extensions`](extensions) directory. These extensions provide features which
are not part of the standard Elastic stack, but can be used to enrich it with extra integrations.
The documentation for these extensions is provided inside each individual subdirectory, on a per-extension basis. Some
of them require manual changes to the default ELK configuration.
## JVM tuning
## How can I specify the amount of memory used by a service?
### How can I specify the amount of memory used by a service?
By default, both Elasticsearch and Logstash start with [1/4 of the total host memory](https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/parallel.html#default_heap_size) allocated to the JVM Heap Size.
By default, both Elasticsearch and Logstash start with [1/4 of the total host
memory](https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/parallel.html#default_heap_size) allocated to
the JVM Heap Size.
The startup scripts for Elasticsearch and Logstash can append extra JVM options from the value of an environment variable, allowing the user to adjust the amount of memory that can be used by each component:
The startup scripts for Elasticsearch and Logstash can append extra JVM options from the value of an environment
variable, allowing the user to adjust the amount of memory that can be used by each component:
| Service | Environment variable |
|---------------|----------------------|
| Elasticsearch | ES_JAVA_OPTS |
| Logstash | LS_JAVA_OPTS |
To accomodate environments where memory is scarce (Docker for Mac has only 2 GB available by default), the Heap Size allocation is capped by default to 256MB per service in the `docker-compose.yml` file. If you want to override the default JVM configuration, edit the matching environment variable(s) in the `docker-compose.yml` file.
To accomodate environments where memory is scarce (Docker for Mac has only 2 GB available by default), the Heap Size
allocation is capped by default to 256MB per service in the `docker-compose.yml` file. If you want to override the
default JVM configuration, edit the matching environment variable(s) in the `docker-compose.yml` file.
For example, to increase the maximum JVM Heap Size for Logstash:
```yml
logstash:
build:logstash/
volumes:
-./logstash/pipeline:/usr/share/logstash/pipeline
ports:
-"5000:5000"
networks:
-elk
depends_on:
-elasticsearch
environment:
LS_JAVA_OPTS:"-Xmx1g-Xms1g"
```
## How can I enable a remote JMX connection to a service?
### How can I enable a remote JMX connection to a service?
As for the Java Heap memory (see above), you can specify JVM options to enable JMX and map the JMX port on the docker host.
As for the Java Heap memory (see above), you can specify JVM options to enable JMX and map the JMX port on the docker
host.
Update the *{ES,LS}_JAVA_OPTS* environment variable with the following content (I've mapped the JMX service on the port 18080, you can change that). Do not forget to update the *-Djava.rmi.server.hostname* option with the IP address of your Docker host (replace **DOCKER_HOST_IP**):
Update the `{ES,LS}_JAVA_OPTS` environment variable with the following content (I've mapped the JMX service on the port
18080, you can change that). Do not forget to update the `-Djava.rmi.server.hostname` option with the IP address of your
