<?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 How to manage multiple regex using same field name in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/676064#M231271</link>
    <description>&lt;P&gt;We have application data coming from Apache Tomcat's and have a regex in place to extract exception name. But there are some tomcats sending data in a slightly different formats and the extraction doesn't work for them.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have updated regex ready for these different formats, but want to keep the field name same, i.e. exception.&lt;/P&gt;&lt;P&gt;How Do I manage multiple extractions against the same sourcetype while keeping the field names same? If I add these regex in transforms, would they end up conflicting with each other?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or should I be creating them into different fields, such as exception1, exception2 and then use&amp;nbsp;&lt;SPAN&gt;coalesce to eventually merge them into a single field?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jan 2024 14:33:56 GMT</pubDate>
    <dc:creator>att35</dc:creator>
    <dc:date>2024-01-31T14:33:56Z</dc:date>
    <item>
      <title>How to manage multiple regex using same field name</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/676064#M231271</link>
      <description>&lt;P&gt;We have application data coming from Apache Tomcat's and have a regex in place to extract exception name. But there are some tomcats sending data in a slightly different formats and the extraction doesn't work for them.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have updated regex ready for these different formats, but want to keep the field name same, i.e. exception.&lt;/P&gt;&lt;P&gt;How Do I manage multiple extractions against the same sourcetype while keeping the field names same? If I add these regex in transforms, would they end up conflicting with each other?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or should I be creating them into different fields, such as exception1, exception2 and then use&amp;nbsp;&lt;SPAN&gt;coalesce to eventually merge them into a single field?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2024 14:33:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/676064#M231271</guid>
      <dc:creator>att35</dc:creator>
      <dc:date>2024-01-31T14:33:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to manage multiple regex using same field name</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/676067#M231273</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/179828"&gt;@att35&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I usually use the different names and coalesce solution in a calculated field.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2024 14:35:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/676067#M231273</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-01-31T14:35:25Z</dc:date>
    </item>
    <item>
      <title>Re: How to manage multiple regex using same field name</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/676090#M231278</link>
      <description>&lt;P&gt;If you can establish sufficiently unique anchors in your regex, you might be able to use pipe-delimited options e.g.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;(anchor 1|anchor 2|anchor 3)(?&amp;lt;field&amp;gt;field pattern)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2024 15:25:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/676090#M231278</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2024-01-31T15:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to manage multiple regex using same field name</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/678162#M231923</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/179828"&gt;@att35&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;good for you, see next time!&lt;/P&gt;&lt;P&gt;Ciao and happy splunking&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;P&gt;P.S.: Karma Points are appreciated by all the contributors &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2024 05:45:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-manage-multiple-regex-using-same-field-name/m-p/678162#M231923</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-02-21T05:45:14Z</dc:date>
    </item>
  </channel>
</rss>

