use unix timestamp instead of java timestamp

[mattdrees]

The API describes the timestamp field as a unix timestamp. However, rollbar-java's default TimestampProvider provides a "java" timestamp, which is based on milliseconds instead of seconds.

The rollbar UI doesn't seem to interpret this:

I dislike how the api loses milliseconds, but it's probably best to be spec-compliant and divide the java timestamp by 1000 to dump the milliseconds.

[brianr]

Good find @mattdrees. I think we can probably keep the milliseconds on the "Notifier Timestamp" if rollbar-java sends it as a float. I believe it'll display without milliseconds on that "Notifier Timestamp" line, but the original value will be available in the Raw JSON section.

[rokob]

@brianr is that true? The fix here is to just send the value as a float or should we divide by 1000 to match the spec here: https://rollbar.com/docs/api/items_post/

[brianr]

@rokob ah sorry, I meant "divide by 1000 and send as a float".

[rokob]

Ah okay yeah