Event Occured Time Wrong

[xuweixi10]

Self-Hosted Version

24.6.0

CPU Architecture

x86_64

Docker Version

24.0.7

Docker Compose Version

2.23.3

Steps to Reproduce

triggle a event

Expected Result

the latency should less than one minute

Actual Result

Event ID

No response

[xuweixi10]

Maybe about timezone But i'm sure all the container in on UTC

[hubertdeng123]

I believe the received timestamp should be when the event is ingested, while the occurred timestamp will be the timestamp when the event has happened. The latency is dependent on multiple factors. There may have been network connection issues that caused the event not to be ingested in time.

[xuweixi10]

I think it's a time zone issue, after i trace the event, i find the the datetime generate caused this problem. here is the code

on eventstore/models.py 119 Sentry 24.6.0
it should be convert to datetime use utc

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[serrrios]

any news by this issue?

[scttcper]

The latency depends on sdks and the devices where they're catching errors. For example, a crashed android app might not send the error event until the next time it is opened causing a large latency. Closing because if you're seeing lots of latency with a Sentry SDK in particular you should open an issue there.