<?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 Limiting precision/decimal in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81283#M20567</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;
Have scenario, when using avg() am getting values as &lt;STRONG&gt;15.000000 but i want it as 15 without decimal&lt;/STRONG&gt;, please help me.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Jan 2013 17:07:47 GMT</pubDate>
    <dc:creator>pramodkumar</dc:creator>
    <dc:date>2013-01-08T17:07:47Z</dc:date>
    <item>
      <title>Limiting precision/decimal</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81283#M20567</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
Have scenario, when using avg() am getting values as &lt;STRONG&gt;15.000000 but i want it as 15 without decimal&lt;/STRONG&gt;, please help me.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2013 17:07:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81283#M20567</guid>
      <dc:creator>pramodkumar</dc:creator>
      <dc:date>2013-01-08T17:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: Limiting precision/decimal</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81284#M20568</link>
      <description>&lt;P&gt;Use eval and the round() function.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;your search&amp;gt; |stats avg(whatever) as yourNumber | eval n=round(yourNumber)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.1/SearchReference/CommonEvalFunctions"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.1/SearchReference/CommonEvalFunctions&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2013 19:32:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81284#M20568</guid>
      <dc:creator>sdaniels</dc:creator>
      <dc:date>2013-01-08T19:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: Limiting precision/decimal</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81285#M20569</link>
      <description>&lt;P&gt;yes but if you are making a "| chart avg(smthing) over somethingelse by something  " then you have to eval each column explicitly, for me it is not possible, there must be a better way&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2013 13:31:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81285#M20569</guid>
      <dc:creator>sbsbb</dc:creator>
      <dc:date>2013-08-09T13:31:38Z</dc:date>
    </item>
    <item>
      <title>Re: Limiting precision/decimal</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81286#M20570</link>
      <description>&lt;P&gt;This is probably better as a separate question with specific details.  You can include this link to let people know you've already done some homework. Maybe you could create a macro where you pass in the values you want to round, in order to simplify the length of your search. Is the length and complexity of the search a concern?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2013 13:38:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Limiting-precision-decimal/m-p/81286#M20570</guid>
      <dc:creator>sdaniels</dc:creator>
      <dc:date>2013-08-09T13:38:11Z</dc:date>
    </item>
  </channel>
</rss>

