You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed this since day 1 of using sematext. Sometimes the android app sends messages that I know in the code have to be A..B and I see them in the sematext console as B..A
I'm not really sure if this is a problem in the android SDK or in your backend or in the UI but given that the SDK is the originator of the data, I created the ticket here to start as much downstream as possible before going up.
Finally, I've noticed that when this happens, the timestamp of both messages is the same (field @timestamp in the json), so maybe the bug comes from not having enough precision in the android clock. Having said that, there are ways around this, like a serial number or some other method to break the tie in two messages with the same timestamp
The text was updated successfully, but these errors were encountered:
I've noticed this since day 1 of using sematext. Sometimes the android app sends messages that I know in the code have to be A..B and I see them in the sematext console as B..A
I'm not really sure if this is a problem in the android SDK or in your backend or in the UI but given that the SDK is the originator of the data, I created the ticket here to start as much downstream as possible before going up.
Finally, I've noticed that when this happens, the timestamp of both messages is the same (field
@timestamp
in the json), so maybe the bug comes from not having enough precision in the android clock. Having said that, there are ways around this, like a serial number or some other method to break the tie in two messages with the same timestampThe text was updated successfully, but these errors were encountered: