<?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: How to do field extraction with regex? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585313#M203905</link>
    <description>&lt;P&gt;Why is it important to use regex and not standard commands? If the event is proper JSON, it will have smtp-header extracted already. (If not, just spath.) &amp;nbsp;Assuming smtp-header exists, you can then use kv, aka&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Extract#extract" target="_self"&gt;extract&lt;/A&gt;&amp;nbsp;to obtain the fields.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rename smtp-header as _raw
| kv kvdelim=":" pairdelim="\n" limit=0 mv_add=true
| fields - _raw _time
| fields *score&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;(The above lists kvdelim=":", but = is also used by default. &amp;nbsp;The above also works directly with _raw as you listed.) &amp;nbsp;Using your sample data, output is&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;adultscore&lt;/TD&gt;&lt;TD&gt;bulkscore&lt;/TD&gt;&lt;TD&gt;clxscore&lt;/TD&gt;&lt;TD&gt;impostorscore&lt;/TD&gt;&lt;TD&gt;lowpriorityscore&lt;/TD&gt;&lt;TD&gt;malwarescore&lt;/TD&gt;&lt;TD&gt;mlxlogscore&lt;/TD&gt;&lt;TD&gt;mlxscore&lt;/TD&gt;&lt;TD&gt;phishscore&lt;/TD&gt;&lt;TD&gt;priorityscore&lt;/TD&gt;&lt;TD&gt;score&lt;/TD&gt;&lt;TD&gt;spamscore&lt;/TD&gt;&lt;TD&gt;suspectscore&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;129&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;472&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 16 Feb 2022 09:48:48 GMT</pubDate>
    <dc:creator>yuanliu</dc:creator>
    <dc:date>2022-02-16T09:48:48Z</dc:date>
    <item>
      <title>How to do field extraction with regex?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585172#M203853</link>
      <description>&lt;P&gt;My events are in json format.&lt;BR /&gt;The&amp;nbsp; json path where my data is , is here&amp;nbsp;&lt;BR /&gt;&amp;nbsp;"alert.smtp-message.smtp-header"&lt;BR /&gt;&lt;BR /&gt;And with in "smtp-header", I have content like this,&amp;nbsp; from which I could use help in extracting some fields using rex.&lt;BR /&gt;============&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;"smtp-header": "Received: from mxdinx66.Gramyabnk.com (mxdinx66.Gramyabnk.com [159.45.78.215])\n\tby mn-svdc-epi-ran11.ist.Gramyabnk.net (Postfix) with ESMTP id 4JyJsN6m8kzVKnNg\n\tfor &amp;lt;tran.cu@Gramyabnk.com&amp;gt;; Mon, 14 Feb 2922 22:66:28 +9999 (UTC)\nReceived: from pps.filterd (mxdinx66.Gramyabnk.com [127.9.9.1])\n\tby mxdinx66.Gramyabnk.com (8.16.9.42/8.16.9.42) with SMTP id 21EMIuas425197\n\tfor &amp;lt;tran.cu@Gramyabnk.com&amp;gt;; Mon, 14 Feb 2922 22:66:28 GMT\nReceived: from mx9a-99994996.pphosted.com (mx9a-99994996.pphosted.com [295.229.165.191])\n\tby mxdinx66.Gramyabnk.com with ESMTP id 6e65wvawac-1\n\t(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA684 bits=256 verify=NOT)\n\tfor &amp;lt;tran.cu@Gramyabnk.com&amp;gt;; Mon, 14 Feb 2922 22:66:27 +9999\nReceived: from pps.filterd (m9216616.ppops.net [127.9.9.1])\n\tby mx9b-99994996.pphosted.com (8.16.1.2/8.16.1.2) with ESMTP id 21EIDxq8928666\n\tfor &amp;lt;tran.cu@Gramyabnk.com&amp;gt;; Mon, 14 Feb 2922 22:66:26 GMT\nAuthentication-Results: ppops.net;\n\tspf=pass smtp.mailfrom=info@efk.admin.ch;\n\tdkim=pass header.d=efk.admin.ch header.s=dkimkey1;\n\tdmarc=pass header.from=efk.admin.ch\nReceived: from mail11.admin.ch (mail11.admin.ch [162.26.62.11])\n\tby mx9b-99994996.pphosted.com (PPS) with ESMTPS id 6e625qnsf9-1\n\t(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA684 bits=256 verify=NOT)\n\tfor &amp;lt;tran.cu@Gramyabnk.com&amp;gt;; Mon, 14 Feb 2922 22:66:26 +9999\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=efk.admin.ch; h=to\n\t:subject:date:to:from:reply-to:subject:message-id:mime-version\n\t:content-type:content-transfer-encoding; s=dkimkey1; bh=uoC6bt5q\n\thKVezRrk1ux9j7rGCMvkx/6cA9/rS1xbvwE=; b=V9mOEgc1tAyvbFpvkKFgHbnD\n\tHDh67iweoPEV7ZYCPpLW8KSBRU+uX+uL64xdJu9E1mp+BvITob98PRfIaCSIi6HC\n\tIf74+dtpxcVyfo9JXZmCj49tJdilXquYWoCu+OhLeONYd9/NMVs4S/IFHnYT/hmN\n\tNBzuP/5C6MKdlHavIwo=\nTo: \"Pretty Eloisa send you naughty videos https://vk.cc/cb5mIY\" &amp;lt;tran.cu@Gramyabnk.com&amp;gt;\nSubject: =?utf-8?Q?Pretty_Eloisa_send_you_naughty_videos_https://vk.cc/cb5mIY,_bitte?= =?utf-8?Q?_best=C6=A4tigen_Sie_ihre_EFK-Newsletter-Anmeldung?=\nDate: Mon, 14 Feb 2922 22:61:28 +9999\nTo: \"Pretty Eloisa send you naughty videos https://vk.cc/cb5mIY\" &amp;lt;tran.cu@Gramyabnk.com&amp;gt;\nFrom: \"Eidg. Finanzkontrolle\" &amp;lt;info@efk.admin.ch&amp;gt;\nReply-To: \"Eidg. Finanzkontrolle\" &amp;lt;info@efk.admin.ch&amp;gt;\nSubject: =?utf-8?Q?Pretty_Eloisa_send_you_naughty_videos_https://vk.cc/cb5mIY,_bitte?=\n =?utf-8?Q?_best=C6=A4tigen_Sie_ihre_EFK-Newsletter-Anmeldung?=\nMessage-ID: &amp;lt;MjQ1NzA5MwAC75229Y8BAMTY9NDg6Nzg4ODM6NzM@www.efk.admin.ch&amp;gt;\nContent-Type: multipart/alternative;\n\tboundary=\"b1_292f6ee91b9de8a92268de4c4ce5b57f\"\nX-TM-AS-GCONF: 99\nX-MSH-Id: E7195F2B6F624BA184EA6D9F12CD98AE\nContent-Transfer-Encoding: 7bit\nX-Proofpoint-GUID: 5sQWXU-CRjHoWtaxmd54Yn68A2IDf2Eu\nX-CLX-Shades: MLX\nX-Proofpoint-ORIG-GUID: 5sQWXU-CRjHoWtaxmd54Yn68A2IDf2Eu\nX-CLX-Response: 1TFkXGxgaEQpMehcaEQpZRBd6GF1SX9ZiBWNEcxEKWFgXbGdhYnBoGkBpaxo 7GxAHGRoRCnBsF6oeXwEBQkZDfXBTEAc ZGhEKcEwXZ1MfZ6t5RRkTE9AQGhEKbX4XGhEKWE9XSxEg\nMIME-Version: 1.9\nX-Brightmail-Tracker: True\nx-env-sender: info@efk.admin.ch\nX-Proofpoint-Virus-Version: vendor=nai engine=6699 definitions=19258 signatures=676461\nX-Proofpoint-Spam-Details: rule=inbound_aggressive_notspam policy=inbound_aggressive score=9\n clxscore=129 suspectscore=9 adultscore=9 bulkscore=9 mlxlogscore=472\n malwarescore=9 phishscore=9 spamscore=9 priorityscore=9 lowpriorityscore=9\n impostorscore=9 mlxscore=9 classifier=spam adjust=9 reason=mlx scancount=1\n engine=8.12.9-2291119999 definitions=main-2292149128",&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;==============================================&lt;BR /&gt;&lt;BR /&gt;I just need the extraction of the fields present in the last 3 lines in bold. The values after the = sign , excluding the \n .&lt;BR /&gt;clxscore&lt;BR /&gt;suspectscore&lt;BR /&gt;adultscore&lt;BR /&gt;bulkscore&lt;BR /&gt;mlgxscore&lt;BR /&gt;malwarescore&lt;BR /&gt;phishscore&lt;BR /&gt;spamscore&lt;BR /&gt;priorityscore&lt;BR /&gt;owpriorityscore&lt;BR /&gt;&amp;nbsp;impostorscore&lt;BR /&gt;mlxscore&lt;BR /&gt;classifier&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 16:23:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585172#M203853</guid>
      <dc:creator>zacksoft_wf</dc:creator>
      <dc:date>2022-02-15T16:23:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to Field Extraction with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585176#M203857</link>
      <description>&lt;LI-CODE lang="markup"&gt;| rex "clxscore=(?&amp;lt;clxscore&amp;gt;\S+) suspectscore=(?&amp;lt;suspectscore&amp;gt;\S+) adultscore=(?&amp;lt;adultscore&amp;gt;\S+) bulkscore=(?&amp;lt;bulkscore&amp;gt;\S+) mlxlogscore=(?&amp;lt;mlxlogscore&amp;gt;\S+).+ malwarescore=(?&amp;lt;malwarescore&amp;gt;\S+) phishscore=(?&amp;lt;phishscore&amp;gt;\S+) spamscore=(?&amp;lt;spamscore&amp;gt;\S+) priorityscore=(?&amp;lt;priorityscore&amp;gt;\S+) lowpriorityscore=(?&amp;lt;lowpriorityscore&amp;gt;\S+).+ impostorscore=(?&amp;lt;impostorscore&amp;gt;\S+) mlxscore=(?&amp;lt;adultsmlxscorecore&amp;gt;\S+) classifier=(?&amp;lt;classifier&amp;gt;\S+)"&lt;/LI-CODE&gt;</description>
      <pubDate>Tue, 15 Feb 2022 14:21:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585176#M203857</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2022-02-15T14:21:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to Field Extraction with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585188#M203862</link>
      <description>&lt;P&gt;If the order of fields is not static, try adding rex for each field like this&lt;/P&gt;&lt;LI-CODE lang="markup"&gt; | rex field="alert.smtp-message.smtp-header" "clxscore\=(?&amp;lt;clxscore&amp;gt;[^\s\\\]+)" | rex field="alert.smtp-message.smtp-header" "suspectscore\=(?&amp;lt;suspectscore&amp;gt;[^\s\\\]+)" | rex field="alert.smtp-message.smtp-header" "scancount\=(?&amp;lt;scancount&amp;gt;[^\s\\\]+)"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 15:30:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585188#M203862</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2022-02-15T15:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: How to do field extraction with regex?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585313#M203905</link>
      <description>&lt;P&gt;Why is it important to use regex and not standard commands? If the event is proper JSON, it will have smtp-header extracted already. (If not, just spath.) &amp;nbsp;Assuming smtp-header exists, you can then use kv, aka&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Extract#extract" target="_self"&gt;extract&lt;/A&gt;&amp;nbsp;to obtain the fields.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rename smtp-header as _raw
| kv kvdelim=":" pairdelim="\n" limit=0 mv_add=true
| fields - _raw _time
| fields *score&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;(The above lists kvdelim=":", but = is also used by default. &amp;nbsp;The above also works directly with _raw as you listed.) &amp;nbsp;Using your sample data, output is&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;adultscore&lt;/TD&gt;&lt;TD&gt;bulkscore&lt;/TD&gt;&lt;TD&gt;clxscore&lt;/TD&gt;&lt;TD&gt;impostorscore&lt;/TD&gt;&lt;TD&gt;lowpriorityscore&lt;/TD&gt;&lt;TD&gt;malwarescore&lt;/TD&gt;&lt;TD&gt;mlxlogscore&lt;/TD&gt;&lt;TD&gt;mlxscore&lt;/TD&gt;&lt;TD&gt;phishscore&lt;/TD&gt;&lt;TD&gt;priorityscore&lt;/TD&gt;&lt;TD&gt;score&lt;/TD&gt;&lt;TD&gt;spamscore&lt;/TD&gt;&lt;TD&gt;suspectscore&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;129&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;472&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 16 Feb 2022 09:48:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-field-extraction-with-regex/m-p/585313#M203905</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2022-02-16T09:48:48Z</dc:date>
    </item>
  </channel>
</rss>

