<?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: Splunk for F5 Networks -- Syslog Logs in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33611#M1329</link>
    <description>&lt;P&gt;This will not work in this case.  There are actually two different sourcetypes originating from the same host.  For the F5, I have both F5:iRule:WebAccess logs and standard syslog logs.  The F5:iRule:WebAccess logs are being recognized as they should.  They are being sent to a unique port and I have overridden the sourcetype.  But, how do I indicate the other type of logs from the same host should be classified with a different sourcetype?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Wed, 15 May 2013 13:59:20 GMT</pubDate>
    <dc:creator>vragosta</dc:creator>
    <dc:date>2013-05-15T13:59:20Z</dc:date>
    <item>
      <title>Splunk for F5 Networks -- Syslog Logs</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33609#M1327</link>
      <description>&lt;P&gt;All,&lt;/P&gt;

&lt;P&gt;Is there a particular sourcetype that should be assigned to the F5 syslog logs?  Right now, the logs are being forwarded to Splunk over port 514 and are simply being assigned a sourcetype of "udp:514".  Also, I'm not certain the format of the logs is correct.  Currently, they look like this:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;May 14 16:34:45 10.238.148.22 May 14 16:34:28 AAA-SLDC-LTM3900-2 info logger: [ssl_req][14/May/2013:16:34:28 -0400] 10.238.140.125 TLSv1 AES128-SHA "/xxx/stuff.jsp" 2503&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;I was expecting a syslog id to appear as part of the logs, such as something like the following:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;May 13 13:41:12 AAA-SLDC-LTM3900-2 notice sod[6060]: 010c0019:5: Active&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;Is it possible all of the logs I am currently receiving simply have no syslog id?&lt;/P&gt;

&lt;P&gt;Lastly, if the sourcetype is not being auto assigned, is it possible to assign a sourcetype to a subset of logs destined to a particular source?  For example, in addition to the F5 syslog logs, I am also forwarding some firewall logs over this port as well.  I obviously don't want to force the sourcetype to be the same for everything destined to port 514.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2013 20:53:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33609#M1327</guid>
      <dc:creator>vragosta</dc:creator>
      <dc:date>2013-05-14T20:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk for F5 Networks -- Syslog Logs</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33610#M1328</link>
      <description>&lt;P&gt;Yes, you can by using your props.conf.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&lt;/CODE&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;BR /&gt;
[host::&lt;STRONG&gt;&amp;lt;IPorHOSTname&amp;gt;&lt;/STRONG&gt;]&lt;BR /&gt;
sourcetype=&lt;STRONG&gt;&amp;lt;your source type&amp;gt;&lt;/STRONG&gt;&lt;BR /&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;Additional Reading:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Advancedsourcetypeoverrides"&gt;Advancedsourcetypeoverrides&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.2/Data/Configureindex-timefieldextraction"&gt;Configureindex-timefieldextraction&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.2/Knowledge/Addfieldsatsearchtime"&gt;Addfieldsatsearchtime&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Hope this helps or gets you started.  Dont forget to vote and accept answers that help.&lt;/P&gt;

&lt;P&gt;Cheers,&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2013 00:07:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33610#M1328</guid>
      <dc:creator>bmacias84</dc:creator>
      <dc:date>2013-05-15T00:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk for F5 Networks -- Syslog Logs</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33611#M1329</link>
      <description>&lt;P&gt;This will not work in this case.  There are actually two different sourcetypes originating from the same host.  For the F5, I have both F5:iRule:WebAccess logs and standard syslog logs.  The F5:iRule:WebAccess logs are being recognized as they should.  They are being sent to a unique port and I have overridden the sourcetype.  But, how do I indicate the other type of logs from the same host should be classified with a different sourcetype?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2013 13:59:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33611#M1329</guid>
      <dc:creator>vragosta</dc:creator>
      <dc:date>2013-05-15T13:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk for F5 Networks -- Syslog Logs</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33612#M1330</link>
      <description>&lt;P&gt;Could you post a couple of samples of both types od syslog data.&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2013 15:35:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-F5-Networks-Syslog-Logs/m-p/33612#M1330</guid>
      <dc:creator>bmacias84</dc:creator>
      <dc:date>2013-05-15T15:35:49Z</dc:date>
    </item>
  </channel>
</rss>

