-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logs and recordings are difficult to correlate #180
Comments
The simplest solution would be to append the id/friendlyname of the connection (ex charlie71846) to the name of the replay file imo. It should be an easy change |
Yes, I already have something almost working but I'm working on having the replay filename in the logs too. The way my ELK dashboard is setup, using the nice "Connection report" you've made, I would hunt for the correct log files. Without that there is a potential collision on the sessionID if we collect over several IPs for months. Just to give you an idea we had 3208 unique sessions in the last 12 hours on a single IP (2.5M+ events total). Of course, filtering by date would be fine but why just not add it anyway ;) Makes searching in the filesystem quicker too. |
There is no clear link between json events and a given recording file.
There are actually two problems:
The text was updated successfully, but these errors were encountered: