<?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: Custom Eval Command or Custom Search Command as Calculated Field? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219548#M64513</link>
    <description>&lt;P&gt;You're correct about the custom search commands being not available for eval function.  I would go with macro if that's possible.&lt;/P&gt;</description>
    <pubDate>Mon, 03 Oct 2016 15:00:50 GMT</pubDate>
    <dc:creator>somesoni2</dc:creator>
    <dc:date>2016-10-03T15:00:50Z</dc:date>
    <item>
      <title>Custom Eval Command or Custom Search Command as Calculated Field?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219546#M64511</link>
      <description>&lt;P&gt;Is it possible to include a custom search command in your app as a calculated field? One that would automatically appear as part of Verbose search results?&lt;/P&gt;

&lt;P&gt;From what I have seen/read it looks like a custom command has to be used as part of the stream of search commands, and is never an extension of eval which is what I think would be required to accomplish above. &lt;/P&gt;

&lt;P&gt;Trying to decide whether to invest time in a custom search command vs just using a macro.&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2016 11:02:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219546#M64511</guid>
      <dc:creator>snoobzilla</dc:creator>
      <dc:date>2016-10-03T11:02:59Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Eval Command or Custom Search Command as Calculated Field?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219547#M64512</link>
      <description>&lt;P&gt;I am confused by what you are asking. The fields that appear on the left-hand side of Verbose search results are fields extracted at search-time. Those are most often set in props.conf of an app. &lt;/P&gt;

&lt;P&gt;So are you asking for help with a search-time calculated field or do you mean an actual custom search (SPL) command? The latter can be included in an app, but takes a few steps.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2016 14:10:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219547#M64512</guid>
      <dc:creator>rjthibod</dc:creator>
      <dc:date>2016-10-03T14:10:07Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Eval Command or Custom Search Command as Calculated Field?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219548#M64513</link>
      <description>&lt;P&gt;You're correct about the custom search commands being not available for eval function.  I would go with macro if that's possible.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2016 15:00:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219548#M64513</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-10-03T15:00:50Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Eval Command or Custom Search Command as Calculated Field?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219549#M64514</link>
      <description>&lt;P&gt;That answers my question. It is not ideal for my use case though.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Oct 2016 15:23:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Custom-Eval-Command-or-Custom-Search-Command-as-Calculated-Field/m-p/219549#M64514</guid>
      <dc:creator>snoobzilla</dc:creator>
      <dc:date>2016-10-17T15:23:32Z</dc:date>
    </item>
  </channel>
</rss>

