#karina_

1 messages · Page 1 of 1 (latest)

nimble folioBOT
verbal pond
#

Can you elaborate? What do you mean by 'time it took for this test request'?

lost needle
#

the time between your servers receiving the request and successfully responding

#

we have seen a number of timeouts for our requests in our test environment, but only since last friday which seems odd

#

just trying to see where the slowdown might be 🤔

verbal pond
#

What types of timeout are you seeing? What specifically is timing out?

lost needle
#

we are seeing requests on our end just taking too long. are you able to tell how long that particular request took in your system?

#

if it is shorter than what our logs are reporting i can rule out stripe as a problem and perhaps start digging into our deployment infrastructure

verbal pond
#

As far as I can tell on our end, we received the request and responded within a fraction of a second (~530 milliseconds). Are you getting a timeout when waiting for the response after you make the request?

lost needle
#

our logs are telling us we are getting the successful response at ~60 seconds 😱

#

i'll bring this back to my team. thanks!

#

oh wait, sorry, i lied. i misunderstood the logs that my coworker gave me. and infact the stripe gem is reporting that the request took over 60 seconds...

#
message="Response from Stripe API" api_version=2020-03-02 elapsed=60.5463303259985 idempotency_key=79e18859-1c55-4590-9517-890479431bec method=post path=/v1/subscriptions/sub_1LuJoPBEIZKO4QrAIfoPJrut request_id=req_tImArc1JpkpoNU status=200
verbal pond
#

Ahhh, okay. Let me dig a bit on this

verbal pond
#

On first glance it looks like the ~60+ second duration is the amount of time it's taking the request to get to us, as our internal handling of the request/response had an end-to-end duration of less than a second