<?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: httpd.conf configuration for logging recommendation? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/httpd-conf-configuration-for-logging-recommendation/m-p/232079#M45232</link>
    <description>&lt;P&gt;If you have this "luxury" you can try to conform your data to the Splunk industry standard one from - &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.2/Data/Listofpretrainedsourcetypes"&gt;List of pretrained source types&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;This can be pretty cheerful if you manage to do it - one of my dreams in my current place ; - )&lt;/P&gt;</description>
    <pubDate>Thu, 18 Aug 2016 00:59:10 GMT</pubDate>
    <dc:creator>ddrillic</dc:creator>
    <dc:date>2016-08-18T00:59:10Z</dc:date>
    <item>
      <title>httpd.conf configuration for logging recommendation?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/httpd-conf-configuration-for-logging-recommendation/m-p/232078#M45231</link>
      <description>&lt;P&gt;All, &lt;/P&gt;

&lt;P&gt;We have legacy servers going years back and newer ones etc. Basically, we have ended up with about 30 different settings in httpd.conf for logging. They asked me what I want the standard to be for Splunk reasons. Started to think about that, and is there any reason why I shouldn't directly ask for CIM friendly key value pairs rights now in the source? &lt;/P&gt;

&lt;P&gt;LogFormat &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;%t src_ip=%h RemoteLogName=%l RemoteUser=%u request=\"%r\" %&amp;gt;s %b \"%{Referer}i\" http_user_agent=\"%{User-Agent}i\"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Example:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[17/Aug/2016:20:20:27 -0400] src_ip=192.168.1.47 RemoteLogName=- RemoteUser=- request="GET /default.html HTTP/1.1" 304 - "-" http_user_agent="Mozilla/5.0 (Macintosh; Inte....
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 18 Aug 2016 00:28:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/httpd-conf-configuration-for-logging-recommendation/m-p/232078#M45231</guid>
      <dc:creator>daniel333</dc:creator>
      <dc:date>2016-08-18T00:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: httpd.conf configuration for logging recommendation?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/httpd-conf-configuration-for-logging-recommendation/m-p/232079#M45232</link>
      <description>&lt;P&gt;If you have this "luxury" you can try to conform your data to the Splunk industry standard one from - &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.2/Data/Listofpretrainedsourcetypes"&gt;List of pretrained source types&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;This can be pretty cheerful if you manage to do it - one of my dreams in my current place ; - )&lt;/P&gt;</description>
      <pubDate>Thu, 18 Aug 2016 00:59:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/httpd-conf-configuration-for-logging-recommendation/m-p/232079#M45232</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2016-08-18T00:59:10Z</dc:date>
    </item>
  </channel>
</rss>

