Add SYN COUNT and use epoch milliseconds

[boverhof]

modified:   tstat_transport/format.py
-- add SYN COUNT on flow

[apertome]

There are multiple things that use this, and that are expecting the start/end times to be in seconds, not ms; this will break them. Is there a reason you need the output in ms, as opposed to converting after you import?

If you do need ms output, it would be good to add as an optional parameter (but leave seconds the default).

The SYN COUNT part looks fine and shouldn't break anything else.

Thanks,
Michael

[boverhof]

I had to make some changes to the NERSC DTN tstat elasticsearch data and I noticed in the raw data is in milliseconds. In ES they were showing up as rounded seconds and figured it would be better to have millisecond resolution, and since I have to resend all the TSTAT data anyway I just changed it.

ES by default looks for EPOCH MS so it works easily for NERSC.

Adding a parameter or to the config.ini would be fine.

mostly I just want to use the netsage tstat_transport on NERSC's DTNs, we've been using a fork since October/2017 which is ok.

[apertome]

If you would like to update your branch to add ms as a configurable option, we would be open to that solution. Let me know when you get that added, and I'll review/merge.

[boverhof]

Okay I'll plan on making 'ms' configurable and notify you when ready.