Forge Home


This module sets up the elastic beat journalbeat for linux based systems

Tore Sæterdal



2,800 latest version

4.8 quality score

Version information

  • 0.2.2 (latest)
  • 0.2.1
  • 0.2.0
  • 0.1.0
released Aug 29th 2019
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
  • Puppet >= 4.10.0 < 7.0.0
  • CentOS

Start using this module


tsaterdal/journalbeat — version 0.2.2 Aug 29th 2019


Welcome to your new module. A short overview of the generated parts can be found in the PDK documentation at .

The README template below provides a starting point with details about what information to include in your README.

Table of Contents

  1. Description
  2. Setup - The basics of getting started with journalbeat
  3. Usage - Configuration options and additional functionality
  4. Limitations - OS compatibility, etc.
  5. Development - Guide for contributing to the module


This module sets ut the Elastic Beat journabeat

Beginning with journalbeat

This module assumes the ELK stack is up and running in you environment, at the very least a logstash server running with a resolvable url


class { 'journalbeat':
      logstash_hosts => [''],

If using custom path for TLS/SSL certificates for logging

class { 'journalbeat':
      logstash_hosts => '',
      tls_ca_file    => '/mypath/exampleca.pem',
      tls_cert_file  => '/mypath/examplecert.pem'
      tls_key_file   => '/mypath/examplekey.pem',


This section is deprecated. Instead, add reference information to your code as Puppet Strings comments, and then use Strings to generate a in your module. For details on how to add code comments and generate documentation with Strings, see the Puppet Strings documentation and style guide

If you aren't ready to use Strings yet, manually create a in the root of your module directory and list out each of your module's classes, defined types, facts, functions, Puppet tasks, task plans, and resource types and providers, along with the parameters for each.

For each element (class, defined type, function, and so on), list:

  • The data type, if applicable.
  • A description of what the element does.
  • Valid values, if the data type doesn't make it obvious.
  • Default value, if any.

For example:

### `pet::cat`

#### Parameters

##### `meow`

Enables vocalization in your cat. Valid options: 'string'.

Default: 'medium-loud'.


In the Limitations section, list any incompatibilities, known issues, or other warnings.


In the Development section, tell other users the ground rules for contributing to your project and how they should submit their work.

Release Notes/Contributors/Etc. Optional

If you aren't using changelog, put your release notes here (though you should consider using changelog). You can also add any additional sections you feel are necessary or important to include here. Please use the ## header.