Forge Home

Modules

Resources

PuppetEcosystemPuppet CommunityUpdates

graylogcollectorsidecar

Installs and configures graylogcollectorsidecar, tags as resources
Project URLRSS FeedReport issues

5,870 downloads

916 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.1.2 (latest)
  • 1.1.1
  • 1.1.0
  • 1.0.0
released Jul 7th 2021
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
  • Puppet >= 5.0.0 < 7.0.0
  • ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'pinguinag-graylogcollectorsidecar', '1.1.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add pinguinag-graylogcollectorsidecar
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install pinguinag-graylogcollectorsidecar --version 1.1.2

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

pinguinag/graylogcollectorsidecar — version 1.1.2 Jul 7th 2021

graylogcollectorsidecar

Module description

Graylog Collector Sidecar is a centrally managed logging agent for graylog.

This module does not have any major dependencies (only concat) and realizes tags as resources, so you can add tags for the same node from multiple different manifests.

Note: only compatible with the old collector-sidecar (up to version 0.1.8), not the new graylog-collector. The new collector does not use tags and instead requires API actions to assign nodes to configurations. There is no way to do this on a per-node basis without race conditions, so it will not be supported.

It is only tested on Debian 9/10 and Ubuntu 16.04 / 18.04 with Puppet 5. Since it uses only build in puppet resources it should run on a wide variety of systems, but we cannot guarantee it. If you sucessfully test it on a different configuration, please let us know and we will update the metadata.

Since it uses $facts['fact'] syntax, it is not compatible with puppet 3.

Usage

Installation

Using Hiera

include graylogcollectorsidecar

Hiera:

graylogcollectorsidecar::api_url: 'http://my-graylog-server.example.com:9000/api'
graylogcollectorsidecar::version: '0.1.6'

Using class

class { 'graylogcollectorsidecar':
    api_url => 'http://my-graylog-server.example.com:9000/api',
    version => '0.1.6',
    node_id => $facts['networking']['hostname'] # this is the default
}

Adding Tags

Tags are implemented as resources. This way, you can add tags over mutliple manifests, like for example profiles.

class { 'profiles::webserver':
  graylogcollectorsidecar::tags { 'apache':
    tags => [
      'apache.access',
      'apache.error'
    ]
  }
}

class { 'profiles::mysql':
  graylogcollectorsidecar::tags { 'mysql':
    tags => [
      'mysql.error',
      'mysql.slowquery'
    ]
  }
}

Uninstall

class { 'graylogcollectorsidecar':
    ensure  => false,
    api_url => 'http://my-graylog-server.example.com:9000/api',
    version => '0.1.6',
    node_id => $facts['networking']['hostname'] # this is the default
}