<?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: Found useful trick to have field values as new fields with {field} in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Found-useful-trick-to-have-field-values-as-new-fields-with-field/m-p/623658#M216798</link>
    <description>&lt;P&gt;There is a tiny sentence associated with that feature in the eval documentation page&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.2/SearchReference/Eval#Field_names" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.2/SearchReference/Eval#Field_names&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I believe I have seen this spoken about as 'dummy encoding', but that is not in those pages.&lt;/P&gt;&lt;P&gt;It is a VERY useful feature, as it supports that syntax within any other text, so you can do stuff like&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval a=random(), b=random(), my_random1_{a}_and_random2_{b}_vars="done"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 08 Dec 2022 02:24:00 GMT</pubDate>
    <dc:creator>bowesmana</dc:creator>
    <dc:date>2022-12-08T02:24:00Z</dc:date>
    <item>
      <title>Found useful trick to have field values as new fields with {field}</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Found-useful-trick-to-have-field-values-as-new-fields-with-field/m-p/623584#M216772</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;we found useful trick to have field values as new fields, for example :&lt;/P&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;LI-CODE lang="markup"&gt;| eval {status}=status | timechart count count(failed) as FAILED | eval failed_percent=FAILED/count*100 &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;How do you call this? Is is documented?&lt;/P&gt;
&lt;P&gt;Thanks &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2022 16:07:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Found-useful-trick-to-have-field-values-as-new-fields-with-field/m-p/623584#M216772</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2022-12-07T16:07:50Z</dc:date>
    </item>
    <item>
      <title>Re: Found useful trick to have field values as new fields with {field}</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Found-useful-trick-to-have-field-values-as-new-fields-with-field/m-p/623658#M216798</link>
      <description>&lt;P&gt;There is a tiny sentence associated with that feature in the eval documentation page&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.2/SearchReference/Eval#Field_names" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.2/SearchReference/Eval#Field_names&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I believe I have seen this spoken about as 'dummy encoding', but that is not in those pages.&lt;/P&gt;&lt;P&gt;It is a VERY useful feature, as it supports that syntax within any other text, so you can do stuff like&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval a=random(), b=random(), my_random1_{a}_and_random2_{b}_vars="done"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Dec 2022 02:24:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Found-useful-trick-to-have-field-values-as-new-fields-with-field/m-p/623658#M216798</guid>
      <dc:creator>bowesmana</dc:creator>
      <dc:date>2022-12-08T02:24:00Z</dc:date>
    </item>
  </channel>
</rss>

