https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36956#M8223 <P>I was able to implement it using the eval round() command. Thanks to anyone who looked into it for me, your help is, as always, appreciated.</P> Wed, 02 Feb 2011 04:49:44 GMT msarro 2011-02-02T04:49:44Z https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36955#M8222 <P>Is there any easy way to limit precision in mathematical operations with eval? I've been requested to limit everything to a maximum of two decimal places.</P> Wed, 02 Feb 2011 04:18:25 GMT https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36955#M8222 msarro 2011-02-02T04:18:25Z https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36956#M8223 <P>I was able to implement it using the eval round() command. Thanks to anyone who looked into it for me, your help is, as always, appreciated.</P> Wed, 02 Feb 2011 04:49:44 GMT https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36956#M8223 msarro 2011-02-02T04:49:44Z https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36957#M8224 <P>Do you want 2 digits out from it, or do you really need the internal numbers to be cut?</P> <P>It has formatting operators and so on, so you can just do eg |eval field=round(.... , 2)</P> Wed, 02 Feb 2011 04:50:44 GMT https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36957#M8224 jrodman 2011-02-02T04:50:44Z https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36958#M8225 <P>That's the solution i ended up using. Thanks!</P> Thu, 03 Feb 2011 22:24:09 GMT https://community.splunk.com/t5/Splunk-Search/Limiting-precision/m-p/36958#M8225 msarro 2011-02-03T22:24:09Z