Closed 15joeybloom closed 4 years ago
Thanks! I think I’d lean towards a PR that keeps sending the timestamp since in some situations that might be helpful information and different from when it was received by sentry (which is what I assume they default to if you don’t provide it).
Would that work for you and would you be open to create a PR for that?
Yeah that works for me! Here's the new version, sending the current time in UNIX format.
FWIW, Sentry acknowledged this issue on their support forum. https://forum.sentry.io/t/string-formatted-timestamp-in-header-no-longer-accepted-by-api-breaking-clojure-raven-library/8383
Thanks, deployed with 1.6.0-alpha4
.
Previously
sentry_timestamp
in the header was sent in the format2019-12-13 12:02:58.94
. This suddenly stopped working on 12/12 around 16:45 CST.Sentry's documentation (see the Authentication section) says that the
sentry_timestamp
should be a UNIX timestamp. We tried sending0
and that worked just fine, but we also tried not sendingsentry_timestamp
at all and that also worked.Here is a PR removing
sentry_timestamp
from the header. What do you think?