# Daily report and Byte Transfer Pairs

**URL:** <https://community.zeek.org/t/daily-report-and-byte-transfer-pairs/925>\
**Category:** Zeek\
**Created:** [February 17, 2006, 6:38pm UTC](https://community.zeek.org/t/daily-report-and-byte-transfer-pairs/925 "2006-02-17T18:38:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![frenzy](https://avatars.discourse-cdn.com/v4/letter/f/8edcca/32.png) [@frenzy](https://community.zeek.org/u/frenzy)\
**Post date:** [February 17, 2006, 6:38pm UTC](https://community.zeek.org/t/daily-report-and-byte-transfer-pairs/925/1 "2006-02-17T18:38:45Z")

</div>

I have been noticing that sometimes the daily report Byte Transfer Pair  
information in the Local bytes and Remote Bytes values can be off by a  
very large factor from the actual traffic size.

Is this caused by the traffic estimation algorithm, and what factors could  
contribute to that larger size? The transfers in question were some HTTP  
traffic that didn't get to be above 100 K in size, and Bro reported it as  
being 1815 M.

This is using the current Bro 1.x branch code.

Thanks for any input you folks can provide.

Randy

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:37pm UTC](https://community.zeek.org/t/daily-report-and-byte-transfer-pairs/925/2 "2022-05-06T15:37:47Z")

</div>