<?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: Field extraction failing on ampersand in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580471#M102411</link>
    <description>&lt;LI-CODE lang="markup"&gt;Jan 10 15:08:21 host.domain.com 2022-01-10 15:07:38 reason=Allowed event_id=000000000000 protocol=HTTPS action=Allowed transactionsize=1111 responsesize=111 requestsize=1111 urlcategory=Custom URL Category serverip=8.8.8.8 clienttranstime=111 requestmethod=POST refererURL=www.google.com/ ClientIP=9.9.9.9 status=204 user=user@domain.com url=www.google.com/gen_204?atyp=csi&amp;amp;ei=rUvcYZ-iM5GV0PEPt9uH8As&amp;amp;s=web&amp;amp;st=13120&amp;amp;fid=2&amp;amp;t=fi&amp;amp;zx=1641827258879&lt;/LI-CODE&gt;</description>
    <pubDate>Mon, 10 Jan 2022 15:14:05 GMT</pubDate>
    <dc:creator>wilcomply13</dc:creator>
    <dc:date>2022-01-10T15:14:05Z</dc:date>
    <item>
      <title>Field extraction failing on ampersand</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580311#M102386</link>
      <description>&lt;P&gt;I have an issue with a URL field being extracted improperly and failing when an ampersand is present in the URL field. Transforms indicates the following delims:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;DELIMS = "\t", "="&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Btool run on the SH member also shows that no other extract commands or delims are identified. All fields are extracted properly except for URL fields that have an ampersand, which excludes everything beyond the ampersand for the field value.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 20:58:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580311#M102386</guid>
      <dc:creator>wilcomply13</dc:creator>
      <dc:date>2022-01-07T20:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction failing on ampersand</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580416#M102397</link>
      <description>Hi&lt;BR /&gt;can you post your current props.conf, transforms.conf and sample data? Is this on search or ingest phase issue?&lt;BR /&gt;r. Ismo</description>
      <pubDate>Mon, 10 Jan 2022 09:51:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580416#M102397</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2022-01-10T09:51:54Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction failing on ampersand</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580448#M102404</link>
      <description>&lt;P&gt;This is a search time field extraction:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[proxy-web]
FIELDALIAS-ClientIP_as_src=ClientIP AS src
FIELDALIAS-ClientIP_as_src_ip = ClientIP AS src_ip
FIELDALIAS-aob_gen_proxy_web_alias_1 = protocol AS transport
FIELDALIAS-aob_gen_proxy_web_alias_2 = user AS src_user
FIELDALIAS-aob_gen_proxy_web_alias_3 = dlpengine AS severity
FIELDALIAS-aob_gen_proxy_web_alias_4 = threatname AS signature
FIELDALIAS-aob_gen_proxy_web_alias_5 = contenttype AS http_content_type
FIELDALIAS-aob_gen_proxy_web_alias_6 = hostname AS dest
FIELDALIAS-aob_gen_proxy_web_alias_8 = responsesize AS bytes_in
FIELDALIAS-aob_gen_proxy_web_alias_9 = requestsize AS bytes_out
FIELDALIAS-clientpublicIP_as_src_translated_ip = clientpublicIP AS src_translated_ip
FIELDALIAS-clienttranstime_as_response_time = clienttranstime AS response_time
FIELDALIAS-department_as_src_user_bunit = department AS src_user_bunit
FIELDALIAS-dlpdictionaries_as_signature = dlpdictionaries AS signature
FIELDALIAS-filename_as_file_name = filename AS file_name
FIELDALIAS-md5_as_file_hash = md5 AS file_hash
FIELDALIAS-refererURL_as_http_referrer = refererURL AS http_referrer
FIELDALIAS-requestmethod_as_http_method = requestmethod AS http_method
FIELDALIAS-serverip_as_dest_ip = serverip AS dest_ip
FIELDALIAS-threatcategory_as_category = threatcategory AS category
FIELDALIAS-transactionsize_as_bytes = transactionsize AS bytes
FIELDALIAS-urlcategory_as_category = urlcategory AS category
FIELDALIAS-useragent_as_http_user_agent = useragent AS http_user_agent
REPORT-ta_builder_internal_use_kv_format_results_for_proxy_web = ta_builder_internal_use_kv_format_results_for_proxy_web
category = Network &amp;amp; Security
description = Web/Proxy Logs&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;transforms.conf&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ta_builder_internal_use_kv_format_results_for_proxy_web]
DELIMS = "\t", "="&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Sample output discrepancy with custom regex to extract full URL vs. URL extracted by default given above props/transforms:&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sample data" style="width: 999px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/17490i04EA27625DC6E3F8/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2022-01-10 at 8.26.13 AM.png" alt="Sample data" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Sample data&lt;/span&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jan 2022 13:31:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580448#M102404</guid>
      <dc:creator>wilcomply13</dc:creator>
      <dc:date>2022-01-10T13:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction failing on ampersand</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580463#M102408</link>
      <description>Can you post also _raw?</description>
      <pubDate>Mon, 10 Jan 2022 15:04:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580463#M102408</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2022-01-10T15:04:16Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction failing on ampersand</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580471#M102411</link>
      <description>&lt;LI-CODE lang="markup"&gt;Jan 10 15:08:21 host.domain.com 2022-01-10 15:07:38 reason=Allowed event_id=000000000000 protocol=HTTPS action=Allowed transactionsize=1111 responsesize=111 requestsize=1111 urlcategory=Custom URL Category serverip=8.8.8.8 clienttranstime=111 requestmethod=POST refererURL=www.google.com/ ClientIP=9.9.9.9 status=204 user=user@domain.com url=www.google.com/gen_204?atyp=csi&amp;amp;ei=rUvcYZ-iM5GV0PEPt9uH8As&amp;amp;s=web&amp;amp;st=13120&amp;amp;fid=2&amp;amp;t=fi&amp;amp;zx=1641827258879&lt;/LI-CODE&gt;</description>
      <pubDate>Mon, 10 Jan 2022 15:14:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Field-extraction-failing-on-ampersand/m-p/580471#M102411</guid>
      <dc:creator>wilcomply13</dc:creator>
      <dc:date>2022-01-10T15:14:05Z</dc:date>
    </item>
  </channel>
</rss>

