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
When analyzing logs it is hard to see if an issue is related to slow network requests. It is technically possible to calculate the time network requests took by taking the start and end timestamps, but this is very time consuming and almost impossible if you do not know which request could be slow.
Solution
Add the time it took for the request to complete in the "Finished API request" log. This will allow spotting slow network requests easily while glancing at the logs.
The text was updated successfully, but these errors were encountered:
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Problem
When analyzing logs it is hard to see if an issue is related to slow network requests. It is technically possible to calculate the time network requests took by taking the start and end timestamps, but this is very time consuming and almost impossible if you do not know which request could be slow.
Solution
Add the time it took for the request to complete in the "Finished API request" log. This will allow spotting slow network requests easily while glancing at the logs.
The text was updated successfully, but these errors were encountered: