From e5a067b4b963ef0a55d2c92c5ae5108c5e6010f6 Mon Sep 17 00:00:00 2001 From: Michael Kaye <1917473+michaelkaye@users.noreply.github.com> Date: Fri, 21 Jan 2022 11:48:40 +0000 Subject: [PATCH] Combine eleweb/eledesktop, add notes about process/thread ID. --- docs/submitted_reports.md | 20 +++++++------------- 1 file changed, 7 insertions(+), 13 deletions(-) diff --git a/docs/submitted_reports.md b/docs/submitted_reports.md index 327392d..082aafa 100644 --- a/docs/submitted_reports.md +++ b/docs/submitted_reports.md @@ -2,15 +2,13 @@ Rageshakes can come from a number of applications, and we provide some practical notes on the generated format. -At present these should not be considered absolute nor a structure to follow; but an attempt to document the -currently visible formats as of January 2022. - +At present these should not be considered absolute nor a structure to follow; but an attempt to document the currently visible formats as of January 2022. ## Feedback Log files are not transmitted; the main feedback is entirely within the user message body. -## Element Web +## Element Web / Element Desktop Log files are transmitted in reverse order (0000 is the youngest) @@ -24,19 +22,12 @@ L = log level, (W=Warn, I=Info, etc) New log files are started each restart of the app. - -## Element desktop - - - ## Element iOS Crash Log is special and is sent only once (and deleted on the device afterwards) `crash.log` - - Following logs are available, going back in time with ascending number. console.log with no number is the current log file. ``` @@ -64,18 +55,21 @@ Log file 0000 is odd, it contains the logcat data if sent. Log line format: ``` 01-17 14:59:30.657 14303 14303 W Activity: Slow Operation: -<-- TIMESTAMP ---> <-?-> <-?-> L <-- Message -- +<-- TIMESTAMP ---> <-P-> <-T-> L <-- Message -- L = Log Level (W=Warn, I=Info etc) +P = Process ID +T = Thread ID ``` Remaining log files are transmitted according to their position in the round-robin logging to file - there will be (up to) 7 files written to in a continious loop; one of the seven will be the oldest, the rest will be in order. Log line format: ``` 2022-01-17T13:06:36*838GMT+00:00Z 12226 D/ /Tag: Migration: Importing legacy session -< ---- TIMESTAMP ---------------> <-?-> L <-- Message ---- +< ---- TIMESTAMP ---------------> <-P-> L <-- Message ---- L = log level, (W=Warn, I=Info, etc) +P = Process ID ``` Once the fix to #40 is in place, we will see the following files: