#logstash

/

      • dharknes has quit
      • rtoren_ joined the channel
      • pcrook joined the channel
      • zeroecco has quit
      • rtoren has quit
      • jbehrends has quit
      • soulair joined the channel
      • soulair
        Hey everyone. What's the best way to send windows event logs to a logstash server?
      • I've seen some about nxlog
      • what are some other options?
      • kireevco has quit
      • warkolm
        nxlog is probably the best
      • soulair
        Ok thats cool. It seems like a strong choice
      • filenox joined the channel
      • torrancew
        nxlog is probably the best bet - just watch out, IIRC they still enable SSLv3 (not sure you can disable it, either :/)
      • thumpba joined the channel
      • oh, looks like they fixed it
      • thumpba_ joined the channel
      • soulair
        Oh nice
      • Im gonna have to learn it a bit
      • dharknes joined the channel
      • filenox has quit
      • JDiPierro joined the channel
      • JDiPierro has quit
      • michaelhart joined the channel
      • JDiPierro joined the channel
      • robgssp joined the channel
      • rtoren_ has quit
      • rtoren joined the channel
      • rayha joined the channel
      • btobolaski joined the channel
      • daveX7 has quit
      • daveX7 joined the channel
      • JDiPierro has quit
      • gentunian has quit
      • jonatin has quit
      • dharknes has quit
      • Baribal__ joined the channel
      • mdedetrich joined the channel
      • Baribal_ has quit
      • iamchrisf joined the channel
      • torqu3e has quit
      • wt0f has quit
      • robgssp has quit
      • rojem joined the channel
      • robgssp joined the channel
      • Knuit
        What is the proper way to GROK this value? It's the URI Query string from an IIS log: d=p6ed21QCM_0B4-6FKW-yJKL_khaQJL-sfsmf&t=6355844
      • warkolm
        what do you want to break out of it
      • lucascastro joined the channel
      • Knuit
        Nothing, I just want to capture the entire value into a key
      • rojem has quit
      • shaun has quit
      • It's contained within a tab-delimited line
      • soulair has quit
      • warkolm
        maybe greedydata?
      • have you tried using the grok debgger?
      • logstashbot
        Title: Grok Debugger (at grokdebug.herokuapp.com)
      • kjstone00 joined the channel
      • Knuit
        I have yeah, greedydata looks like it grabs the remainder of the line though, this value is in the middle
      • Rapture has quit
      • supersheep has quit
      • joefides joined the channel
      • warkolm
        define the other fields, then you can just take that one
      • jmreicha joined the channel
      • shaun joined the channel
      • mdedetrich has quit
      • joefides_ has quit
      • kepper joined the channel
      • Socket-
        whats wrong with this syntax? if [type] == "ocsplog" or [type] == "ejbcalog" {
      • mdedetrich joined the channel
      • warkolm
        looks ok, what are you seeing
      • ycombinator has quit
      • is-mw2 joined the channel
      • Socket-
        {:timestamp=>"2015-04-28T21:43:42.228000-0400", :message=>"Error: Expected one of #, } at line 86, column 47 (byte 2931) after filter {\n if [type] == \"rsyslog\" {\n\tgrok { match => [ \"message\", \"%RSYSLOGBASE\" ]"}
      • tombar joined the channel
      • logstashbot
        Title: Paste #XUL - Apache Paste Bucket (at apaste.info)
      • is-mw has quit
      • Socket-
        having a hard time finding the syntax error
      • fev3r101 has quit
      • Knuit
        warkolm: Thanks, looks like that works. Does greedydata just take the remaining un-matched contents of the line?
      • jerryitt has quit
      • larivee joined the channel
      • dendazen joined the channel
      • kepper has quit
      • rtoren has quit
      • _JZ_ joined the channel
      • rtoren joined the channel
      • kjstone00 joined the channel
      • JempInDaKella has quit
      • JempInDaKella joined the channel
      • filenox joined the channel
      • chenryn joined the channel
      • Socket-
        I have a syslog listener, it seems LS is able to index the data without me creating a pattern, I want to use a custom pattern which i have created, but i think the default one is getting in the way. How do i tell LS to not run syslog events through %{SYSLOGBASE} before hitting my filter
      • russorat has quit
      • BaM`
        Socket-: you can override the %{SYSLOGBASE} pattern by providing your own with the same name
      • filenox has quit
      • ...or any pattern for that matter
      • Socket-
        when i do that i get a grok parse error
      • BaM`
        possible issue with your pattern then?
      • Socket-
        i'll share
      • cpe has quit
      • cpe joined the channel
      • almost done with paste
      • logstashbot
        Title: #26811 CentOS Pastebin (at pastebin.centos.org)
      • Socket-
        BaM`: see anything?
      • BaM`
        pls hold...
      • a couple of things stand out
      • zebrarage joined the channel
      • you need %{RSYSLOGBASE} not %RSYSLOGBASE in your grok match
      • Socket-
        ohh, thats huge
      • thanks, i didnt see that
      • BaM`
        also your custom pattern is never going to match just the "message" field - it looks like it's trying to match an entire syslog line
      • e.g., it's starting with %{SYSLOGTIMESTAMP}
      • but you're trying to match "pam_unix(su:session): session opened for user root by dan(uid=0)"
      • Socket-
        i think i need to match the entire line
      • some of my syslog events look like this
      • BaM`
        timestamp and program etc have already been matched somewhere earlier
      • Socket-
        <77>Apr 28 16:22:44 nix run-parts(/etc/cron.daily)[7980] finished prelink
      • BaM`
        ah yep
      • Socket-
        how do i match the line instead?
      • BaM`
        well that matches for the sample you just gave me
      • nemothekid has quit
      • Socket-
        or what do you think is the best way to handle these and normal syslog data
      • brokencycle has quit
      • BaM`
        you can either give them different types and let them hit different conditions
      • Socket-
        yeah, it matches and seems to index everything right, but it still has grok parse tag on it
      • BaM`
        or you can just have multiple match patterns inside one grok
      • if you don't mind the extra overhead of some failing
      • russorat joined the channel
      • Socket-
        Im not sure i follow you, can you break that down differently?
      • BaM`
        if it reaches the end of a grok without mathing anything, it will get a _grokparsefail
      • ok
      • do you have different syslog stuff coming from different sources?
      • Socket-
        they all come from rsyslog remote forwarder
      • BaM`
        ah I see
      • do you know which hosts are sending which syslog formats?
      • actually, I have a better plan
      • pls hold
      • Socket-
        all using: RSYSLOG_TraditionalFileFormat
      • BaM`
        are some in JSON format already though?
      • your custom message snippet suggests that
      • Socket-
        im not sure what causes that
      • i think it's auto done with the input maybe?
      • rtoren has quit
      • BaM`
        nah - there are things like severity and facility in there
      • so it's either already tagged up when it reaches logstash, or it's hitting another filter somewhere
      • Socket-
        so, here is a raw syslog event: Apr 27 19:03:34 nix yum[54088]: Updated: dracut-004-356.el6_6.1.noarch