<?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: Calculated field in DB Connect in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104599#M183184</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;

&lt;P&gt;You should put this configuration of props.conf in the Search Head, not in the heavy forwarder.&lt;/P&gt;</description>
    <pubDate>Wed, 24 Jul 2013 14:23:29 GMT</pubDate>
    <dc:creator>gfuente</dc:creator>
    <dc:date>2013-07-24T14:23:29Z</dc:date>
    <item>
      <title>Calculated field in DB Connect</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104596#M183181</link>
      <description>&lt;P&gt;I have done testing the calculated fields for Splunk DB Connect in my local machine. Basically I added props.conf file to the following folder:  %SPLUNK_HOM%\etc\apps\dbx\local&lt;/P&gt;

&lt;P&gt;In the file, I have something like this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[MySoureType]
EVAL-cpu_time_s = CPU / 1000
EVAL-duration_s = Duration / (1000 * 1000)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It works perfectly in my local environment, I can see those fields (cpu_time_s, duration_s) show up in the search. However, when I implement in the actual server (a dedicated heavy forwarder installed with Dbx in a distributed environment), I can't find those fields anymore.&lt;/P&gt;

&lt;P&gt;Any reason why it behaves differently? How should I troubleshoot this situation.&lt;BR /&gt;
Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:24:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104596#M183181</guid>
      <dc:creator>dan60201</dc:creator>
      <dc:date>2020-09-28T14:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated field in DB Connect</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104597#M183182</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;

&lt;P&gt;Probably, in your distributed enviroment, the fields CPU and Duration are not beign exctracted properly, and because of that the calculated fields doesn´t work either&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 08:15:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104597#M183182</guid>
      <dc:creator>gfuente</dc:creator>
      <dc:date>2013-07-24T08:15:01Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated field in DB Connect</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104598#M183183</link>
      <description>&lt;P&gt;gfuente, Thanks for reply. Both CPU and Duration were showing up just fine. I also tried with fixed value like EVAL_test = 'test', but no such field showed up.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 14:18:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104598#M183183</guid>
      <dc:creator>dan60201</dc:creator>
      <dc:date>2013-07-24T14:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated field in DB Connect</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104599#M183184</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;

&lt;P&gt;You should put this configuration of props.conf in the Search Head, not in the heavy forwarder.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 14:23:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104599#M183184</guid>
      <dc:creator>gfuente</dc:creator>
      <dc:date>2013-07-24T14:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated field in DB Connect</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104600#M183185</link>
      <description>&lt;P&gt;I checked all splunk servers (search head/indexer) and can only find props.conf with EVAL- in indexer. So, I configured the dedicated heavy forwarder with dbx installed and enabled indexAndForward = true in outputs.conf. I am expecting it will do calculated field in this box before sending to splunk receiver.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 16:34:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104600#M183185</guid>
      <dc:creator>dan60201</dc:creator>
      <dc:date>2013-07-24T16:34:18Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated field in DB Connect</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104601#M183186</link>
      <description>&lt;P&gt;Forgot to mention, those existing EVAL- from other apps managed by deployment server are working fine. Only DB Connect that I configured in this dedicated box did not work as I expected.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 16:36:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104601#M183186</guid>
      <dc:creator>dan60201</dc:creator>
      <dc:date>2013-07-24T16:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated field in DB Connect</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104602#M183187</link>
      <description>&lt;P&gt;If I want to move/test EVAL-field to indexer (instead of defining it in the dedicated forwarder server with dbx), it's not clear to me what exactly the steps I should do? How does indexer know I want add additional calculated fields? Where do I need to put such props.conf?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 22:18:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104602#M183187</guid>
      <dc:creator>dan60201</dc:creator>
      <dc:date>2013-07-24T22:18:37Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated field in DB Connect</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104603#M183188</link>
      <description>&lt;P&gt;Somehow I need to move that configuration into indexers, rather than in DB connect dedicated server. Now those calculated fields work as expected.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jul 2013 20:49:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field-in-DB-Connect/m-p/104603#M183188</guid>
      <dc:creator>dan60201</dc:creator>
      <dc:date>2013-07-25T20:49:11Z</dc:date>
    </item>
  </channel>
</rss>

