<?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: Apache Logs Data Parsing in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695810#M115505</link>
    <description>&lt;P&gt;Can Anyone help on my request please.&lt;/P&gt;</description>
    <pubDate>Fri, 09 Aug 2024 09:44:06 GMT</pubDate>
    <dc:creator>anandhalagaras1</dc:creator>
    <dc:date>2024-08-09T09:44:06Z</dc:date>
    <item>
      <title>Apache Logs Data Parsing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695805#M115504</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;We have recently started ingesting Apache access and request logs from an application, but the data parsing isn't working as expected.&lt;/P&gt;
&lt;P&gt;Could you please let me know the field names for these events so I can try to extract them manually? Alternatively, do we have any format or add-on available that would enable automatic field extraction? If so, that would also be fine with me.&lt;/P&gt;
&lt;P&gt;For your information, our Splunk Search Head is hosted in the cloud and managed by Splunk Support.&lt;/P&gt;
&lt;P&gt;I have provided the log structure for both log sources for reference. Please help to check and update.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Request Logs:&lt;BR /&gt;[09/Aug/2024:07:50:37 +0000] xx.yyy.zzz.aa TLSv1.2 ABCDE-FGH-IJK256-LMN-SHA123 "GET /share/page/ HTTP/1.1" xxxxx&lt;BR /&gt;[09/Aug/2024:07:50:37 +0000] xx.yyy.zzz.aa TLSv1.2 xxxxx-xxx-xxx256-xxx-xxx123 "GET /share/page/ HTTP/1.1" -&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Access Logs:&lt;BR /&gt;xx.yyy.zzz.aa - - [09/Aug/2024:07:57:00 +0000] "GET /share/page/ HTTP/1.1" 200 xxxxx&lt;BR /&gt;aaa.bbb.ccc.dd - - [09/Aug/2024:07:56:53 +0000] "GET /share/page/ HTTP/1.1" 200 -&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2026 16:38:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695805#M115504</guid>
      <dc:creator>anandhalagaras1</dc:creator>
      <dc:date>2026-04-01T16:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Logs Data Parsing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695810#M115505</link>
      <description>&lt;P&gt;Can Anyone help on my request please.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2024 09:44:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695810#M115505</guid>
      <dc:creator>anandhalagaras1</dc:creator>
      <dc:date>2024-08-09T09:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Logs Data Parsing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695825#M115506</link>
      <description>&lt;P&gt;1. This is not a Professional Support service. People do have their lives and respond when they have some spare time.&lt;/P&gt;&lt;P&gt;2. For typical apache httpd logs there are two built-in sourcetypes - access_combined and apache_error.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2024 12:21:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695825#M115506</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-08-09T12:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Logs Data Parsing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695863#M115513</link>
      <description>&lt;P&gt;Splunk have default definitions for access_combined, access_combined_wcookie, access_common and apache_error. You can look those (.../system/default/props.conf and transforms.conf). You could use this as base for your own sourcetype definitions.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2024 16:58:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/695863#M115513</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-08-09T16:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Logs Data Parsing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/696111#M115545</link>
      <description>&lt;P&gt;I cloned the "access_combined" sourcetype for the access logs, and now the fields are being extracted as desired.&lt;/P&gt;&lt;P&gt;However, I'm unable to parse the request logs as expected. If anyone has some time, I would appreciate assistance with parsing the request logs. It would be really helpful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Request Logs Format:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;[09/Aug/2024:07:50:37 +0000] xx.yyy.zzz.aa TLSv1.2 ABCDE-FGH-IJK256-LMN-SHA123 "GET /share/page/ HTTP/1.1" xxxxx&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;[09/Aug/2024:07:50:37 +0000] xx.yyy.zzz.aa TLSv1.2 xxxxx-xxx-xxx256-xxx-xxx123 "GET /share/page/ HTTP/1.1" -&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 09:50:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/696111#M115545</guid>
      <dc:creator>anandhalagaras1</dc:creator>
      <dc:date>2024-08-13T09:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Logs Data Parsing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/696141#M115549</link>
      <description>&lt;P&gt;These might be useful:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.splunk.com/t5/All-Apps-and-Add-ons/parsing-log-text-to-get-a-specific-info/m-p/484283" target="_blank"&gt;https://community.splunk.com/t5/All-Apps-and-Add-ons/parsing-log-text-to-get-a-specific-info/m-p/484283&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Getting-Data-In/How-to-configure-Splunk-to-properly-parse-logs-that-contain-one/m-p/200151" target="_blank"&gt;https://community.splunk.com/t5/Getting-Data-In/How-to-configure-Splunk-to-properly-parse-logs-that-contain-one/m-p/200151&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Also see if an app helps, the extractions and such like are useful to inspect and use as needed:&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://splunkbase.splunk.com/app/3186#/overview" target="_blank"&gt;https://splunkbase.splunk.com/app/3186#/overview&lt;/A&gt;&lt;/P&gt;&lt;P&gt;(from&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Apache-access-logs-in-Splunk/m-p/266983" target="_blank"&gt;https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Apache-access-logs-in-Splunk/m-p/266983&lt;/A&gt;)&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 15:08:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Apache-Logs-Data-Parsing/m-p/696141#M115549</guid>
      <dc:creator>JohnEGones</dc:creator>
      <dc:date>2024-08-13T15:08:54Z</dc:date>
    </item>
  </channel>
</rss>

