{"push_id":1212258423,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"01bfb785da2b7943d6cb1a428ead4025a98ddfc5","before":"ecf85cffbdf96c8c2f81ae0ce1cdd9ecc74dda51","commits":[{"sha":"5fab7794a33695498c2a6ef528b3b0f0f5490f89","author":{"name":"Brian Candler","email":"8617313c0de5dbbe9df9b92002192fbd488c66d5@pobox.com"},"message":"Aggregate using in+out bytes for bidirectional flows\n\nSome sources of data, e.g.  ASA NSEL, record a bidirectional flow record\nwith separate counters for in/out bytes and in/out packets.  This patch\nmakes aggregation over \"packets\", \"bytes\", \"bps\" etc look at the *sum* of\nthe input and output counters.  Previously they would use only the input\ncounters.\n\nQuery types which explicitly look at one direction, like \"ibyte\" and\n\"obyte\", are unchanged.\n\nProcessing of unidirectional flows is not affected, because these store\nvalues in the \"in\" counters only - the \"out\" counters are zero, so using the\nsum of in+out is the same.\n\nThe resulting code is simpler: it doesn't have to calculate both in/out\nvalues everywhere. It also uses accessor functions for all values, which\nmeans no special cases for r->counter[cindex].","distinct":true,"url":"https://api.github.com/repos/phaag/nfdump/commits/5fab7794a33695498c2a6ef528b3b0f0f5490f89"},{"sha":"01bfb785da2b7943d6cb1a428ead4025a98ddfc5","author":{"name":"Peter Haag","email":"591826729f0b109578cc7a813b58fc51df25a6fd@pyxis.ch"},"message":"Merge pull request #28 from candlerb/candlerb/in_out_bytes\n\nAggregate using in+out bytes for bidirectional flows","distinct":true,"url":"https://api.github.com/repos/phaag/nfdump/commits/01bfb785da2b7943d6cb1a428ead4025a98ddfc5"}]}
{"actor":{"display_login":"phaag"}}