UDP Input getting broken into two entries


#1

Pretty much the topic. Here's the input:

udp {
                type => "logon10"
                port => 7515
                buffer_size => 65536
                receive_buffer_bytes => 65536
        }

However when receiving large messages from a syslog server I see that the message is cut in two:

{
      "date" => "Jan 13 13:41:36",
   "message" => "Jan 13 13:41:36 x.x.x.x HOSTNAME.DOMAIN.Local#011MSWinEventLog#0111#011Security#011275#011Wed Feb 25 09:52:06 2015#0114624#011Microsoft-Windows-Security-Auditing#011DOMAIN\\HOSTNAME#011N/A#011Success Audit#011HOSTNAME.DOMAIN.Local#011Logon#011#011An account was successfully logged on.    Subject:   Security ID:  S-1-5-18   Account Name:  HOSTNAME$   Account Domain:  DOMAIN   Logon ID:  0x3e7    Logon Type:   10    New Logon:   Security ID:  S-1-5-21-xxxxxxxxx-xxxxxxxx-xxxxxxxx-xxxx   Account Name:  user   Account Domain:  DOMAIN   Logon ID:  0xxxxxxx   Logon GUID:  {xxxxxxxxxxxxxxxxxxxxxxxxxxxx}    Process Information:   Process ID:  0x2728   Process Name:  C:\\Windows\\System32\\winlogon.exe    Network Information:   Workstation Name: HOSTNAME   Source Network Address: x.x.x.x   Source Port:  57169    Detailed Authentication Information:   Logon Process:  User32    Authentication Package: Negotiate   Transited Services: -   Package Name (NTLM only): -   Key Length:  0    This event is generated when a logon session is created. It is generated on the computer that was accessed.    The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.    The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).    The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.    The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.    The authentication information fields provide detailed information about this specific logon request.   - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.   - Transited services indicate which intermediate services have participated in this logon request.   - Package name in",
      "type" => "logon10",
      "tags" => [
    [0] "_geoip_lookup_failure"
],
    "src_ip" => "x.x.x.x",
 "dst_geoip" => {},
"@timestamp" => 2017-01-13T21:10:35.855Z,
  "@version" => "1",
      "host" => "x.x.x.x",
 "src_geoip" => {},
  "username" => "user"
}
{
     "dst_geoip" => {},
    "@timestamp" => 2017-01-13T21:10:35.855Z,
      "@version" => "1",
          "host" => "x.x.x.x",
     "src_geoip" => {},
       "message" => "dicates which sub-protocol was used among the NTLM protocols.   - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.#011245#\n",
          "type" => "logon10",
          "tags" => [
        [0] "_grokparsefailure",
        [1] "_geoip_lookup_failure"
    ]
}

You can see here that the message was cut at the word "indicates". Is there a max that I'm missing? Thank you.


(Andrew Cholakian) #2

Is your first message greater than the maximum size of a UDP datagram? UDP cannot handle messages of unbounded sizes.


#3

Why yes....yes it is :smiley: That's fantastic....I guess it's time to install Beats. Thank you....didn't think of looking at the network layer:

  2 2017-01-13 22:51:10.563841 x.x.x.x → x.x.x.56  UDP 610 33726→7515 Len=2048
  3 2017-01-13 22:51:10.564230 x.x.x.x → x.x.x.56  UDP 229 33726→7515 Len=187

Thanks again.


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.