<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Syslog Field Extractions in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411129#M50166</link>
    <description>&lt;P&gt;I'm running into the same exact problem. By any chance, did you ever find a resolution to this issue?&lt;/P&gt;</description>
    <pubDate>Wed, 09 Oct 2019 16:20:52 GMT</pubDate>
    <dc:creator>luongg</dc:creator>
    <dc:date>2019-10-09T16:20:52Z</dc:date>
    <item>
      <title>Syslog Field Extractions</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411128#M50165</link>
      <description>&lt;P&gt;So given that netscaler 12.1 should work, I have events coming in from 4 netscalers via syslog and I named the sourcetype=citrix:netscaler:syslog which I believe is correct upon review of the default props.conf. Fields do not appear to be extracting for the sourcetype, is this an issue with rsyslog setup perhaps the way the timestamps or is there something I'm missing?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Apr 17 16:04:23 netscaler01.somelan.local  04/17/2019:16:04:17   0-PPE-0 : default TCP CONN_DELINK 11964927 0 :  Source 192.168.20.7:64151 - Vserver 192.168.20.4:443 - NatIP 192.168.20.2:49222 - Destination 192.168.20.5:443 - Delink Time 04/17/2019:16:04:17  - Total_bytes_send 0 - Total_bytes_recv 2683

Apr 17 16:04:22 netscaler01.somelan.local  04/17/2019:16:04:16   0-PPE-0 : default TCP CONN_TERMINATE 11964913 0 :  Source 192.168.20.6:80 - Destination 192.168.20.3:35760 - Start Time 04/17/2019:16:03:32  - End Time 04/17/2019:16:04:16  - Total_bytes_send 428 - Total_bytes_recv 377 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 18 Apr 2019 16:21:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411128#M50165</guid>
      <dc:creator>shawngarrettsgp</dc:creator>
      <dc:date>2019-04-18T16:21:13Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Field Extractions</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411129#M50166</link>
      <description>&lt;P&gt;I'm running into the same exact problem. By any chance, did you ever find a resolution to this issue?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2019 16:20:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411129#M50166</guid>
      <dc:creator>luongg</dc:creator>
      <dc:date>2019-10-09T16:20:52Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Field Extractions</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411130#M50167</link>
      <description>&lt;P&gt;do you have a copy of the &lt;CODE&gt;props.conf&lt;/CODE&gt; in question handy?&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 19:44:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411130#M50167</guid>
      <dc:creator>wmyersas</dc:creator>
      <dc:date>2019-10-17T19:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Field Extractions</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411131#M50168</link>
      <description>&lt;P&gt;nope, ran out of forks&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 20:27:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411131#M50168</guid>
      <dc:creator>shawngarrettsgp</dc:creator>
      <dc:date>2019-10-17T20:27:21Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Field Extractions</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411132#M50169</link>
      <description>&lt;P&gt;&lt;A href="https://splunkbase.splunk.com/app/4366/" target="_blank"&gt;https://splunkbase.splunk.com/app/4366/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I'm just using the default&lt;BR /&gt;
Splunk_TA_citrix_netscaler_Enosys/default/props.conf&lt;/P&gt;

&lt;P&gt;cat Splunk_TA_citrix_netscaler_Enosys/default/app.conf | grep -i version&lt;/P&gt;

&lt;H2&gt;This Add-on version 1.1 works only when Citrix Netscaler syslog is forwarded to Splunk SIEM via Splunk Heavy Forwarder, Splunk Enterprise or Splunk Cloud.&lt;/H2&gt;

&lt;P&gt;version = 1.1&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;clip of the sourcetype&lt;BR /&gt;
[citrix:netscaler:syslog]&lt;BR /&gt;
KV_MODE=none&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;REPORT-citrix_netscaler_syslog = citrix_netscaler_syslog,netscaler_syslog_quoted_fields,netscaler_syslog_unquoted_fields&lt;BR /&gt;
EXTRACT-1-syslog_event_name = \s+[\d\/]{10}(:\d{2}){3}\s+\w{3}\s+\S+\s+\S+\s+:([^:]+)?\s+\w+\s+(?\w+)\s+\d+\s+0\s+:\s+.+&lt;/P&gt;

&lt;P&gt;EVAL-bytes = Total_bytes_recv+Total_bytes_send&lt;BR /&gt;
EVAL-dest_ip = mvindex(split(Destination,":"),0)&lt;BR /&gt;
EVAL-dest_port = mvindex(split(Destination,":"),1)&lt;BR /&gt;
EVAL-src_ip = mvindex(split(Source,":"),0)&lt;BR /&gt;
EVAL-src_port = mvindex(split(Source,":"),1)&lt;BR /&gt;
EVAL-vendor = "Citrix Systems"&lt;BR /&gt;
FIELDALIAS-cim_builder = event_source AS app User AS user Total_bytes_recv AS bytes_in Total_bytes_send AS bytes_out ns_name AS dvc&lt;BR /&gt;
EVAL-dest = if(isnull(Destination),if(match(event_name,".&lt;EM&gt;CONNSTAT$"),Remote_ip,if(match(event_name,"^LOG(IN|OUT).&lt;/EM&gt;"),host,mvindex(split(Destination,":"),0))),mvindex(split(Destination,":"),0))&lt;BR /&gt;
EVAL-duration = (strptime(Duration,"%H:%M:%S")-strptime("00:00:00","%H:%M:%S"))*1000&lt;BR /&gt;
EVAL-src = if(isnull(Source),Client_ip,mvindex(split(Source,":"),0))&lt;BR /&gt;
FIELDALIAS-device_serial_number_chassis = device_serial_number AS chassis&lt;BR /&gt;
EVAL-action = case(match(event_name,".*CONNSTAT$"), "allowed", match(event_name,"^LOG(IN|OUT)$"), "success", match(event_name,"LOGIN_FAILED"), "failure")&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:39:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411132#M50169</guid>
      <dc:creator>shawngarrettsgp</dc:creator>
      <dc:date>2020-09-30T02:39:18Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Field Extractions</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411133#M50170</link>
      <description>&lt;P&gt;a little weird that here's no &lt;CODE&gt;TIMESTAMP&lt;/CODE&gt; definition in there - especially when the time seems to show up more than once in the event line&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 20:39:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411133#M50170</guid>
      <dc:creator>wmyersas</dc:creator>
      <dc:date>2019-10-17T20:39:07Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Field Extractions</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411134#M50171</link>
      <description>&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/6573/alternative-ways-to-assigning-sourcetype.html"&gt;https://answers.splunk.com/answers/6573/alternative-ways-to-assigning-sourcetype.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I found a similar question answered, please take a look at the above link.&lt;/P&gt;

&lt;P&gt;Hope this helps, Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 22:44:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411134#M50171</guid>
      <dc:creator>sandeepmakkena</dc:creator>
      <dc:date>2019-10-17T22:44:20Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Field Extractions</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411135#M50172</link>
      <description>&lt;P&gt;I am using rsyslog to read in my netscaler events.&lt;BR /&gt;
I have inputs.conf set up to read in all of my rsyslog events and set the sourcetype for each.&lt;BR /&gt;
This is my Netscaler code in my local/inputs.conf&lt;/P&gt;

&lt;H1&gt;Netscaler&lt;/H1&gt;

&lt;P&gt;[monitor:///opt/syslog/netscaler/&lt;EM&gt;/&lt;/EM&gt;.log]&lt;BR /&gt;
sourcetype=citrix:netscaler:syslog&lt;BR /&gt;
index=network&lt;BR /&gt;
host_segment=4&lt;BR /&gt;
disabled=false&lt;/P&gt;

&lt;P&gt;Then I use a local/props.conf to establish the time and the local/transfroms  to extract the netscaler hostname.&lt;BR /&gt;
From there the rest of the fields are extracted by the netscaler add-on.&lt;/P&gt;

&lt;P&gt;If you want to try this route, I can work you up a time and hostname extract based on your log example.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2019 22:28:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Syslog-Field-Extractions/m-p/411135#M50172</guid>
      <dc:creator>edhealea</dc:creator>
      <dc:date>2019-11-12T22:28:14Z</dc:date>
    </item>
  </channel>
</rss>

