Logstash configuration update - config files, inputs

As a fun addendum to the ELK posts, I'm posting up some of the updated config files in the hopes that it'll help some folk starting down the 'ELK in a Windows environment' path.

Here's our config file structure:

  • 00-inputs.conf (all inputs in here, really just two)
  • 01-filters_start.conf (how I keep the brackets organized)
  • 02-filters_drop.conf (drop stuff first)
  • 10-filters_grok.conf (fixing grokparsefailures to start)
  • 15-filters_mutate.conf
  • 20-filters_tagging.conf
  • 30-filters_metrics.conf
  • 89-filters_end.conf (bracket organization)
  • 90-outputs_start.conf
  • 91-outputs_elasticsearch.conf
  • 92-outputs_nagios.conf
  • 93-outputs_graphite.conf
  • 99-outputs_end.conf

As part of my own self-review, I'll try to go through all of this, but I'll break it up into two posts - one on filters, one on outputs.  The remainder of this post will have config file breakout and Input section discussion.

Config file breakout

Since I'm still a Linux newb, my co-worker kindly informed me that most programs that have a conf.d (config directory) just cat together the contents to build the configuration file.  I found a post (cannot recall where) that showed this basic methodology, so I copied that.  It's working well, means that when I go to edit stuff it's simple, and not pages and pages of code to sift through.

One item I really want to implement is using Git for our Logstash configs - infrastructure as code and all that.  I suspect I'd have to re-point Logstash to the local repo location...something to look into.

Inputs

input {
    tcp {
        type => eventlog
        port => 1935
        codec => json_lines
    }
    syslog {
        type => syslog
        port => 5514
    }
}
Pretty simple - NXlog sends to TCP1935, and our syslog intermediary translates standard syslog on port TCP?514 to TCP?5514.  This is done purely because our originating syslog server is really old and gets angry when you try to change the port it's sending on.  Also, you cannot have logstash listen on 514 because that's a restricted port and I'm not fancy enough to make that work.  (it might not even be a good idea to force it)

Next post, Filters...

Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many of us work in seem to apply this as law - an
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible on
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99A
Read more