Forge Home


Puppet module for managing nxlog on windows


11,641 latest version

3.1 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

  • 0.3.3 (latest)
  • 0.3.2
  • 0.3.1
  • 0.2.0
  • 0.1.7
  • 0.1.6 (deleted)
  • 0.1.5
  • 0.1.4
  • 0.1.3 (deleted)
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Dec 18th 2016
This version is compatible with:
  • Puppet Enterprise >=3.0.0 <4.7.0
  • Puppet >=3.0.0 <4.7.0
  • Windows

Start using this module

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

Add this module to your Puppetfile:

mod 'dschaaff-nxlog', '0.3.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add dschaaff-nxlog
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install dschaaff-nxlog --version 0.3.3

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.



dschaaff/nxlog — version 0.3.3 Dec 18th 2016


Build Status

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with nxlog
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing and how
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module


This module manages the installation and configuration of nxlog community edition on windows hosts.

Module Description

This module manages the installation and configuration of nxlog community edition on Windows hosts. A common use case is to use this to ship off logs to something like splunk, or logstash.

Manages the following

  • nxlog config files
  • nxlog inputs
  • nxlog outputs
  • nxlog routes


What nxlog affects

  • nxlog-ce package installation
  • nxlog.conf
  • nxlog inputs
  • nxlog outputs
  • nxlog routes

Setup Requirements

Including the base class will handle the installation of nxlog but doesn't do much else on its own.

include nxlog

Beginning with nxlog

Include the base class and any inputs, outputs, and routes.

include nxlog
nxlog::input {'eventlogs':
  input_name   => 'eventlogs',
  input_module => 'im_msvistalog',
  query        => '<QueryList><Query Id="0"><Select Path="Security">*</Select></Query>y</QueryList>',
nxlog::output {'out':
  output_name   => 'out',
  output_module => 'om_tcp',
  output_host    => '',
  output_port   => '514',
  output_exec   => 'to_syslog_snare();',
# must route to existing output defined above
nxlog::route {'route1':
  route_name => 'route1',
  route_path => 'eventlogs => out',


For more details on the use of nxlog and its parameters please view the documentation



Public Classes

  • nxlog

Private Classes

  • nxlog::config
  • nxlog::params
  • nxlog::service
  • nxlog::install

Defined Types

  • nxlog::input
  • nxlog::output
  • nxlog::route

Class: nxlog

This is the main class. It will install nxlog and manage the service.


  • root: Sets the root install path in nxlog.conf
    • Default: "C:\\Program Files (x86)\\nxlog"
  • module_dir: By default the nxlog binaries have a compiled-in value for the directory to search for loadable modules. This can be overrridden with this directive. The module directory contains subdirectories for each module type (extension, input, output, processor) and the module binaries are located in those.
    • Default: %ROOT%\modules
  • cache_dir: Specifies where the cache file is written to
    • Default: %ROOT\data
  • pid_file: Directive has no effect on Windows
    • Default: %ROOT%\data\
  • spool_dir: nxlog will change its working directory to the value specified with this directive. This is useful with files created through relative filenames, e.g. with om_file and in case of core dumps. This directive has no effect with the nxlog-processor.
    • Default: %ROOT%\data
  • log_file: Specifies where nxlog will write its internal log file
    • Default: %ROOT%\data\nxlog.log

Defined Type: nxlog::input


  • input_name: Required What the input is called. This is how it will be referenced in route directives
    • Default: undef
  • input_module: Required What nxlog module the input will use.
    • Default: undef
  • query: Optional
    • Default: undef

Defined Type: nxlog::output


  • output_name: Required What the output will be called.
    • Default: undef
  • output_module: Required What nxlog module the output will use.
    • Default: undef
  • output_host: Required Hostname or IP of the output destination host.
    • Default: undef
  • output_port: Required Destination port
    • Default: undef
  • output_exec: Required
    • Default: undef

Defined Type: nxlog::route


  • route_name: Required What the route will be called.
    • Default: undef
  • route_path: Required How the data will be route. Should take the form of input_name => output_name. Input_names should be comma separated when there is more than one.
    • Default: undef
  • route_priority: optional
    • Default: undef


I welcome all contributions and appreciate pull requests.