<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">How about a user redef'able format string for doubles in logs? Even more flexible would be to make it a function. Let the user decide the format they need, and adapt their scripts accordingly, with the default being the current behavior.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 6, 2017 at 10:10 AM, Daniel Thayer <span dir="ltr"><<a href="mailto:dnthayer@illinois.edu" target="_blank">dnthayer@illinois.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 11/6/17 8:16 AM, Seth Hall wrote:<br>
> Right now, Bro will print scientific notation in JSON logs but we've<br>
> always tended to avoid it in the standard Bro log format. What does<br>
> everyone think about switching to allow scientific notation in the<br>
> standard log format? Daniel recently did some exploration of various<br>
> versions of awk and they all support scientific notation (I think that<br>
> was part of my concern a long time ago).<br>
><br>
> Thoughts?<br>
><br>
> .Seth<br>
<br>
</span>Actually, right now Bro uses scientific notation in JSON logs only<br>
for very large values (such as 3.1e+15). For values very close to<br>
zero (such as 1.2e-7), Bro will write "0" to a JSON log.<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
bro-dev mailing list<br>
<a href="mailto:bro-dev@bro.org">bro-dev@bro.org</a><br>
<a href="http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev" rel="noreferrer" target="_blank">http://mailman.icsi.berkeley.<wbr>edu/mailman/listinfo/bro-dev</a><br>
</div></div></blockquote></div><br></div>