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 have observed many request logs in Kong's access log where the request_time is much larger than the upstream_desponse_time. For example, upstream_desponse_time only took 9ms, while request_time is greater than 500ms or 1000ms. Most of these requests are post and put, and I don't know why or how to troubleshoot them
thank u
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have observed many request logs in Kong's access log where the request_time is much larger than the upstream_desponse_time. For example, upstream_desponse_time only took 9ms, while request_time is greater than 500ms or 1000ms. Most of these requests are post and put, and I don't know why or how to troubleshoot them
thank u
Beta Was this translation helpful? Give feedback.
All reactions