<?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: Why is extracted field formatted incorrectly? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-is-extracted-field-formatted-incorrectly/m-p/588327#M204896</link>
    <description>&lt;P&gt;If you look at events, you'll find the field msg with "id" as value. &amp;nbsp;In SPL, you can use rex to extract id as a field, e.g.,&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "msg=id=(?&amp;lt;id&amp;gt;\d+)"&lt;/LI-CODE&gt;</description>
    <pubDate>Thu, 10 Mar 2022 03:32:26 GMT</pubDate>
    <dc:creator>yuanliu</dc:creator>
    <dc:date>2022-03-10T03:32:26Z</dc:date>
    <item>
      <title>Why is extracted field formatted incorrectly?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-extracted-field-formatted-incorrectly/m-p/588322#M204892</link>
      <description>&lt;P&gt;I have the following log that Splunk is not recognizing well :&lt;/P&gt;
&lt;P&gt;msg=id=123342521352 operation=write&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How can I write a query so that ID is parsed by itself?&lt;/P&gt;
&lt;P&gt;The goal is to be able to build a table like :&lt;/P&gt;
&lt;TABLE border="1" width="100%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="50%"&gt;id&lt;/TD&gt;
&lt;TD width="50%"&gt;operation&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%"&gt;123342521352&lt;/TD&gt;
&lt;TD width="50%"&gt;write&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately, when I tried&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;table id operation&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;The id is always empty as it does not seem to be parsed correctly&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2022 00:28:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-extracted-field-formatted-incorrectly/m-p/588322#M204892</guid>
      <dc:creator>yk010123</dc:creator>
      <dc:date>2022-03-10T00:28:45Z</dc:date>
    </item>
    <item>
      <title>Re: Why is extracted field formatted incorrectly?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-extracted-field-formatted-incorrectly/m-p/588327#M204896</link>
      <description>&lt;P&gt;If you look at events, you'll find the field msg with "id" as value. &amp;nbsp;In SPL, you can use rex to extract id as a field, e.g.,&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "msg=id=(?&amp;lt;id&amp;gt;\d+)"&lt;/LI-CODE&gt;</description>
      <pubDate>Thu, 10 Mar 2022 03:32:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-extracted-field-formatted-incorrectly/m-p/588327#M204896</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2022-03-10T03:32:26Z</dc:date>
    </item>
  </channel>
</rss>

