#mordil
1 messages · Page 1 of 1 (latest)
We've gathered a lot of information from the user which we've compiled in this doc https://peeksters.notion.site/Virtualis-VR-Investigations-f692f961ef774d0db0d824b8e3fbf365?pvs=4
Ongoing doc that has the reports from Virtualis, with Sentry & New Relic investigations.
Our ask is to see if Stripe has any additional insight from their logs with the device as to issues that may be arising
All of the timestamps are +/- 5 minutes of the actual event, and are listed on the left-hand side Table of Contents
Their device IDs and Location ID are listed in a table in the doc
None of the reports seem to include the reader serial number, and there are three listed at the start of the doc - am I just looking in the wrong place?
The individual reports all mention the same reader, but I don't know which serial number that correlates with
They have 3 on their account
One sec, I may be able to grab it from Sentry metadata...
WSC513208040004 is the serial number showing up in all our Sentry logs, so I assume that's the one in use in all the reports
gotcha - I can spot check some of these reports, but I'm not going to be able to do a detailed check of all 18 in this channel
was there a specific one you wanted me to start with?
Maybe Report 3, from last Friday at 1628 US Central
and Report 13, from Monday at 1704 US Central
Also, generally, at what latency level do you expect to see issues with the hardware? This partner is regularly seeing 500+ms latency, even communicating with the hardware reader
Looked at both reports - I'm not seeing anything that's jumping out from me in our logs. Just some logs indicating payment failed because the transaction timed out
Is this something that your user is ONLY seeing on the one device, and not their other two? If their other two devices are working fine on the same network setup that points to something maybe being wrong with the one device
@bronze jay just checking in - does that make sense?
@flint coral That makes sense. What's the general latency we should be aiming for reliability?
I don't know if they've tried the others, I'm following down that avenue to see if they can try another model or we send them a new one.
They're also looking to hardwire the readers to get off of Wifi
I think the worst part is that the hardware seems to be "freezing" if they hit these timeouts, requiring the reader to be restarted
Yeah I can imagine that's not a good experience - I don't think we have specific latency requirements for this (sorry I don't have exact numbers)