Forge Home

awesant

Install the awesant log shipper for Logstash with a configuration file.

10,110 downloads

10,110 latest version

3.9 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.1.0 (latest)
released Apr 22nd 2013

Start using this module

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

Add this module to your Puppetfile:

mod 'erwbgy-awesant', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add erwbgy-awesant
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install erwbgy-awesant --version 0.1.0

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

erwbgy/awesant — version 0.1.0 Apr 22nd 2013

awesant

Install the awesant log shipper for Logstash with a configuration file.

To use just:

include awesant

and then specify the location of the config template in hiera - for example:

awesant::config_template: '/etc/puppet/templates/myapp/awesant-agent.conf.erb'

Alternatively you call it as a parameterised class:

class { 'awesant':
  config_template => '/etc/puppet/templates/myapp/awesant-agent.conf.erb'
}

Installation

Installation assumes that an 'awesant' package is available from the package repository. See http://download.bloonix.de/ for pre-built packages for RedHat-like and Debian-like hosts.

Configuration

See https://github.com/bloonix/awesant for documentation on awesant configuration.

By default the following template is used to give you a starting point:

input {
    file {
        type awesant
        tags syslog-messages
        path /var/log/messages
    }
    file {
        type awesant
        tags syslog-secure
        path /var/log/secure
    }
}

output {
    socket {
        type awesant
        host logstash.domain.com
        port 5544
    }
}

logger {
    file {
        filename /var/log/awesant/agent.log
        maxlevel info
    }
}

The corresponding Logstash configuration could be:

input {
  tcp {
    format => "json_event"
    host => logstash.domain.com
    port => 5544
    type => "awesant"
  }
}
filter {
  grok {
    match => [ "@timestamp", "^%{DATE_EU:date}" ]
    type => "awesant"
  }
}
output {
  file {
    tags => 'syslog-messages'
    message_format => "%{@message}"
    path => "/apps/logstash/logs/syslog/messages-%{date}.log"
  }
  file {
    tags => 'syslog-secure'
    message_format => "%{@message}"
    path => "/apps/logstash/logs/syslog/secure-%{date}.log"
  }
}

You can use any facter facts in your template - for example 'fqdn' or a custom fact like 'logstash_host'.

Support

License: Apache License, Version 2.0

GitHub URL: https://github.com/erwbgy/puppet-tomcat