When Bugfender collects log information, it also gathers some metadata on the application and device running:
Please note you can define custom key-value data associated to the device, for additional application-specific context.
Log information collected by Bugfender contains:
Time stamp: indicates when the log took place, according to the clock of the device where your application is running
Tag names: they help you classify log lines in groups. You can use them to name modules, functionalities, etc.
Log level: indicate the severity of the log line. Info, warning and error levels are supported.
When clicking on a log, additional information is displayed:
Method name, file name and line number: so that you can easily locate the code responsible for the message
Where is the timestamp originated?
The Bugfender SDK uses the clock of the device to capture when a log happened.
We do this mainly because the SDK is designed to work offline, so the moment when a log is captured and when it is sent for processing to our servers might vary, sometimes by hours or even days.
Our servers override the time in the following special situations:
Logs are timestamped with a date in the future
Logs are timestamped with a very old date. For example, some devices generate logs in January 1970 while initializing.
When overridden, the time in the logs is the time they were processed by our servers.
You may also be interested