Elastic stack (ELK) on Docker

Run the latest version of the Elastic stack with Docker and Docker Compose.

It gives you the ability to analyze any data set by using the searching/aggregation capabilities of Elasticsearch and
the visualization power of Kibana.

:information_source: The Docker images backing this stack include Stack Features (formerly X-Pack)
with paid features enabled by default (see How to disable paid
features to disable them). The trial license is valid for 30 days.

Based on the official Docker images from Elastic:

• Elasticsearch
• Logstash
• Kibana

Other available stack variants:

• searchguard: Search Guard support

Contents

1. Requirements
   • Host setup
   • SELinux
   • Docker for Desktop
     • Windows
     • macOS
2. Usage
   • Bringing up the stack
   • Cleanup
   • Initial setup
     • Setting up user authentication
     • Injecting data
     • Default Kibana index pattern creation
3. Configuration
   • How to configure Elasticsearch
   • How to configure Kibana
   • How to configure Logstash
   • How to disable paid features
   • How to scale out the Elasticsearch cluster
4. Extensibility
   • How to add plugins
   • How to enable the provided extensions
5. JVM tuning
   • How to specify the amount of memory used by a service
   • How to enable a remote JMX connection to a service
6. Going further
   • Using a newer stack version
   • Plugins and integrations
   • Swarm mode

Requirements

Host setup

• Docker Engine version 17.05+
• Docker Compose version 1.12.0+
• 1.5 GB of RAM

By default, the stack exposes the following ports:

• 5000: Logstash TCP input
• 9200: Elasticsearch HTTP
• 9300: Elasticsearch TCP transport
• 5601: Kibana

:information_source: Elasticsearch's bootstrap checks were purposely disabled to facilitate the
setup of the Elastic stack in development environments. For production setups, we recommend users to set up their host
according to the instructions from the Elasticsearch documentation: Important System Configuration.

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:

$ chcon -R system_u:object_r:admin_home_t:s0 docker-elk/

Docker for Desktop

Windows

Ensure the Shared Drives feature is enabled for the C: drive.

macOS

The default Docker for Mac configuration allows mounting files from /Users/, /Volumes/, /private/, and /tmp
exclusively. Make sure the repository is cloned in one of those locations or follow the instructions from the
documentation to add more locations.

Usage

Bringing up the stack

Clone this repository onto the Docker host that will run the stack, then start services locally using Docker Compose:

$ docker-compose up

You can also run all services in the background (detached mode) by adding the -d flag to the above command.

:information_source: You must run docker-compose build first whenever you switch branch or update a base image.

If you are starting the stack for the very first time, please read the section below attentively.

Cleanup

Elasticsearch data is persisted inside a volume by default.

In order to entirely shutdown the stack and remove all persisted data, use the following Docker Compose command:

$ docker-compose down -v

Initial setup

Setting up user authentication

:information_source: Refer to How to disable paid features to disable authentication.

The stack is pre-configured with the following privileged bootstrap user:

• user: elastic
• password: changeme

Although all stack components work out-of-the-box with this user, we strongly recommend using the unprivileged built-in
users instead for increased security.

1. Initialize passwords for built-in users

$ docker-compose exec -T elasticsearch bin/elasticsearch-setup-passwords auto --batch

Passwords for all 6 built-in users will be randomly generated. Take note of them.

2. Unset the bootstrap password (optional)

Remove the ELASTIC_PASSWORD environment variable from the elasticsearch service inside the Compose file
(docker-compose.yml). It is only used to initialize the keystore during the initial startup of Elasticsearch.

3. Replace usernames and passwords in configuration files

Use the kibana user inside the Kibana configuration file (kibana/config/kibana.yml) and the logstash_system user
inside the Logstash configuration file (logstash/config/logstash.yml) in place of the existing elastic user.

Replace the password for the elastic user inside the Logstash pipeline file (logstash/pipeline/logstash.conf).

:information_source: Do not use the logstash_system user inside the Logstash pipeline file, it does not have
sufficient permissions to create indices. Follow the instructions at Configuring Security in Logstash
to create a user with suitable roles.

See also the Configuration section below.

4. Restart Kibana and Logstash to apply changes

$ docker-compose restart kibana logstash

:information_source: Learn more about the security of the Elastic stack at Tutorial: Getting started with
security.

Injecting data

Give Kibana about a minute to initialize, then access the Kibana web UI by hitting
http://localhost:5601 with a web browser and use the following default credentials to log in:

• user: elastic
• password: <your generated elastic password>

Now that the stack is running, you can go ahead and inject some log entries. The shipped Logstash configuration allows
you to send content via TCP:

# Using BSD netcat (Debian, Ubuntu, MacOS system, ...)
$ cat /path/to/logfile.log, nc -q0 localhost 5000

# Using GNU netcat (CentOS, Fedora, MacOS Homebrew, ...)
$ cat /path/to/logfile.log, nc -c localhost 5000

You can also load the sample data provided by your Kibana installation.

Default Kibana index pattern creation

When Kibana launches for the first time, it is not configured with any index pattern.

Via the Kibana web UI

:information_source: You need to inject data into Logstash before being able to configure a Logstash index pattern via
the Kibana web UI.

Navigate to the Discover view of Kibana from the left sidebar. You will be prompted to create an index pattern. Enter
logstash-* to match Logstash indices then, on the next page, select @timestamp as the time filter field. Finally,
click Create index pattern and return to the Discover view to inspect your log entries.

Refer to Connect Kibana with Elasticsearch and Creating an index pattern for detailed
instructions about the index pattern configuration.

On the command line

Create an index pattern via the Kibana API:

$ curl -XPOST -D- 'http://localhost:5601/api/saved_objects/index-pattern' \
    -H 'Content-Type: application/json' \
    -H 'kbn-version: 7.5.1' \
    -u elastic:<your generated elastic password> \
    -d '{"attributes":{"title":"logstash-*","timeFieldName":"@timestamp"}}'

The created pattern will automatically be marked as the default index pattern as soon as the Kibana UI is opened for the first time.

Configuration

:information_source: Configuration is not dynamically reloaded, you will need to restart individual components after
any configuration change.

How to configure Elasticsearch

The Elasticsearch configuration is stored in elasticsearch/config/elasticsearch.yml.

You can also specify the options you want to override by setting environment variables inside the Compose file:

elasticsearch:

  environment:
    network.host: _non_loopback_
    cluster.name: my-cluster

Please refer to the following documentation page for more details about how to configure Elasticsearch inside Docker
containers: Install Elasticsearch with Docker.

How to configure Kibana

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.

Please refer to the following documentation page for more details about how to configure Kibana inside Docker
containers: Running Kibana on Docker.

How to configure Logstash

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 file for its own logging.

Please refer to the following documentation page for more details about how to configure Logstash inside Docker
containers: Configuring Logstash for Docker.

How to disable paid features

Switch the value of Elasticsearch's xpack.license.self_generated.type option from trial to basic (see License
settings).

How to scale out the Elasticsearch cluster

Follow the instructions from the Wiki: Scaling out Elasticsearch

Extensibility

How to 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)
3. Rebuild the images using the docker-compose build command

How to enable the provided extensions

A few extensions are available inside the 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 to specify the amount of memory used by a service

By default, both Elasticsearch and Logstash start with 1/4 of the total host
memory 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:, 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.

For example, to increase the maximum JVM Heap Size for Logstash:

logstash:

  environment:
    LS_JAVA_OPTS: -Xmx1g -Xms1g

How to 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.

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):

logstash:

  environment:
    LS_JAVA_OPTS: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=18080 -Dcom.sun.management.jmxremote.rmi.port=18080 -Djava.rmi.server.hostname=DOCKER_HOST_IP -Dcom.sun.management.jmxremote.local.only=false

Going further

Using a newer stack version

To use a different Elastic Stack version than the one currently available in the repository, simply change the version
number inside the .env file, and rebuild the stack with:

$ docker-compose build
$ docker-compose up

:information_source: Always pay attention to the upgrade instructions for each individual component before
performing a stack upgrade.

Plugins and integrations

See the following Wiki pages:

• External applications
• Popular integrations

Swarm mode

Experimental support for Docker Swarm mode is provided in the form of a docker-stack.yml file, which can
be deployed in an existing Swarm cluster using the following command:

$ docker stack deploy -c docker-stack.yml elk

If all components get deployed without any error, the following command will show 3 running services:

$ docker stack services elk

:information_source: To scale Elasticsearch in Swarm mode, configure zen to use the DNS name tasks.elasticsearch
instead of elasticsearch.