JsonRollManager also now rotates after time (15min default).
The contents of the tarball are a single file that contains
one notification per file line.
The tarball is created after reaching a certain size or after
a fixed amount of time. Any working files are also tarball'ed
when the service restarts.
Change-Id: I6e9d620086cf24bc1468b638e7b148af7230e2ac
Only check the directory size when we first start the
RollManager. From then on, incrementally add the payload
size. This will result in a difference between on-disk size
vs. file sizes. But, it's much faster than checking every N
times ... those stats() checks are very expensive.
Change-Id: I71b1455db0ea073a4f563f115a693027de50638b
Changed the JSON RollManager to write JSON payloads
to a working directory until a certain directory
size is met. Then the directory is tar/gzipped and
moved into a destination directory.
No CRC is available for the tarball.
Change-Id: I119da646104eeaea86f7153a9bcf123d3143a0ba
Records the event as a json payload in a file that
may include a CRC of the payload. This is typically used
when storing events in something like HDFS.
Change-Id: Iaecca2397afa3501e437e27d698f3573760f1ac0
Brought over and refactored event generator code from TwoBillion.
Now supports real-time and fast-time event generation.
Also in an easier-to-use library now.
