Project

General

Profile

Feature #11648

Save client browser logs

Added by Șerban Bursuc about 12 hours ago. Updated about 12 hours ago.

Status:
WIP
Priority:
Normal
Assignee:
Șerban Bursuc
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Șerban Bursuc about 12 hours ago

The browser logs are not saved anywhere and they are the only method of seeing browser -> FWD server message exchanges, nginx doesn't see the communication, only when it ends. FWD doesn't use HTTP for 99% of the runtime so the logging has to come from inside the browser.

The browser code already logs the chattiness of the websocket, but in production environments the logs get lost as clients are not developers, they don't have their browser console open all the time.

The goal is to try and save these logs. Lyra already does it but it does it in an invasive way, it creates the browser instance itself, attaches to it and spoofs the communication, this cannot happen in production. This is challenging because the connection can get cut at any time, so sending logs from browser to server is risky, it can miss the interval of the issue.

#2 Updated by Șerban Bursuc about 12 hours ago

Another point to saving these logs: see this issue #11477, if this happened and the reporter was not a developer and never open the browser log, I'm not sure how it could've been caught otherwise.

Also available in: Atom PDF