-
-
Notifications
You must be signed in to change notification settings - Fork 373
Description
Is your feature request related to a problem? Please describe.
It looks like the 2 (public) log formats that I use the most are not recognized by lnav:
- dmesg ( https://en.wikipedia.org/wiki/Dmesg )
Example:
[ 0.011400] ACPI: Reserving SSDT table memory at [mem 0x9bbc7000-0x9bbc719a]
[ 0.084325] percpu: Embedded 61 pages/cpu s212992 r8192 d28672 u262144
[ 0.227420] ftrace: allocated 196 pages with 3 groups
- logcat ( https://developer.android.com/tools/logcat )
Example:
12-31 00:00:01.979 1482 1482 I SELinux : SELinux: Loaded service_contexts from:
12-31 00:00:03.418 1611 1611 I apexd : Found /system/apex/com.android.runtime.debug
12-31 00:00:04.190 1448 1448 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xb5c2a144)
12-31 00:00:04.190 1448 1448 W RefBase : CallStack::getCurrentInternal not linked, returning null
(Note: other formats can be used such as the output as per https://developer.android.com/tools/logcat#outputFormat )
Describe the solution you'd like
I'd like to know if it is worth spending some time defining these properly (with https://docs.lnav.org/en/latest/formats.html#defining-a-new-format ) and submitting a PR for it.
In particular, may I suggest 2 formats for the same types of logs depending on the formatting used, for instance:
- "dmesg" vs "dmesg --raw"
- "logcat" vs "logcat -v long"
Also, in the case of "logcat", I may have extra lines such as:
--------- beginning of main
12-31 00:00:00.072 1481 1481 W auditd : type=2000 audit(0.0:1): state=initialized audit_enabled=0 res=1
Do we have to handle them in a special way (so that they do not prevent the format to be recognized) ?
Thanks in advance