Skip to content
Puppet module to manage logstash
Puppet Ruby
Find file
Pull request Compare This branch is 2 commits ahead, 206 commits behind elastic:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


A puppet module for managing and configuring Logstash

Build Status


This overview shows you which puppet module and logstash version work together.

| Puppet module | Logstash         |
| 0.0.1 - 0.1.0 | 1.1.9            |
| 0.2.0         | 1.1.10           |
| 0.3.0 - 0.3.3 | 1.1.12 - 1.1.13  |

Version changes

From version 0.0.6 to 0.1.0 the following has been removed/changed:

initfile (string) => initfiles (hash) defaultsfile (string) => defaultsfiles (hash)


With introduction of the multi-instance feature the default 'logstash' service gets disabled by the module when installed with a package. The module will create and manage the services based on the instance names, the old init script will remain on the system but will not be used.

Setting up logstash without configuration will cause logstash not to start. You will need to define atleast one plugin for Logstash to start.

For OS packages of logstash, see



Installation, make sure service is running and will be started at boot time:

 class { 'logstash': }


 class { 'logstash':
   ensure => 'absent',

Install everything but disable service(s) afterwards:

 class { 'logstash':
   status => 'disabled',

When you want to use an other service manager like 'runit' or 'daemontools':

 class { 'logstash':
   status   => 'unmanaged'


If you require running more then 1 instance on the same machine. If no instances are defined it will default to 'agent'.

 class { 'logstash':
   instances => [ 'instance1', 'instance2' ]

All plugins can be defined to a certain instance. For example:

 logstash::input::file { 'fileinput':
   instances => [ 'instance1' ]

 logstash::input::file { 'fileinput2':
   instances => [ 'instance2' ]

If you rather not use the multi-instance feature you can diable this:

 class { 'logstash':
   multi_instance => false

Other options

If you rather supply your own init script:

 class { 'logstash':
   initfiles => { 'agent' => 'puppet:///path/to/initfile' }

In all cases you can supply a defaults file:

 class { 'logstash':
   defaultsfiles => { 'agent' => 'puppet:///path/to/defaults' }

Installation with a JAR file:

 class { 'logstash':
   provider => 'custom',
   jarfile  => 'puppet:///path/to/jarfile',
   installpath => '/path/to/install/dir'

When no init script is provided when using custom provider, built in init script will be placed. You can however supply your own init script and defaults file.

 class { 'logstash':
   provider      => 'custom',
   jarfile       => 'puppet:///path/to/jarfile',
   initfiles     => { 'agent' => 'puppet:///path/to/initfile' },
   defaultsfiles => { 'agent' => 'puppet:///path/to/defaultsfile' }

If you want java to be installed by the module:

 class { 'logstash':
   java_install => true

If you want a specific java package/version:

 class { 'logstash':
   java_install => true,
   java_package => 'packagename'

If you want to have the logstash files owned by an other user then 'root':

 class { 'logstash':
   logstash_user  => 'logstash',
   logstash_group => 'logstash'

Please note that this does not set the user in the init file!!


Every plugin in Logstash has its own define file.

For more information check the puppet files in the input, output and filter directories.

File transfers

From version 0.2.0 its now possible to automatically transfer files to the host for plugins that require a file.

For example lumberjack requires a certificate, so you can do the following:

 logstash::input::lumberjack { 'lumberjack_input':
   ssl_certificate => 'puppet:///path/to/ssl.cert':

the file 'ssl.cert' will be placed in a pre-defined place and set in the configuration.

Something went wrong with that request. Please try again.