From 8d17561c76b6e2a99e5e618b81b78262bb3deaa8 Mon Sep 17 00:00:00 2001 From: Tim Stack Date: Fri, 6 Jan 2023 09:27:23 -0800 Subject: [PATCH] [docs] mention logfmt in the features page --- docs/03_features.md | 8 +++++++- docs/source/formats.rst | 2 +- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/03_features.md b/docs/03_features.md index 6ef52af1..513cd2ce 100644 --- a/docs/03_features.md +++ b/docs/03_features.md @@ -19,9 +19,11 @@ left-hand side help to show which file a message belongs to. ## Automatic Log Format Detection The log message format is automatically determined by lnav while scanning your -files. The following formats are built in by default: +files. The following are some of the [formats that are built in by default](https://docs.lnav.org/en/latest/formats.html): * Common Web Access Log format +* W3C Extended Log File Format +* logfmt * CUPS page_log * Syslog * Glog @@ -32,6 +34,10 @@ files. The following formats are built in by default: * Strace * sudo +If your log file format is JSON-lines or can be matched by a PCRE regular +expression, you can define your own format in a +[JSON file](https://docs.lnav.org/en/latest/formats.html#defining-a-new-format). + GZIP'ed and BZIP2'ed files are also detected automatically and decompressed on-the-fly. ## Filters diff --git a/docs/source/formats.rst b/docs/source/formats.rst index 2ccde934..5b230224 100644 --- a/docs/source/formats.rst +++ b/docs/source/formats.rst @@ -28,7 +28,7 @@ supported: self-describing, so **lnav** will read the header to determine the shape of the file. * The - `W3C Extend Log File Format `_ + `W3C Extended Log File Format `_ is supported in lnav versions v0.10.0+. The W3C log format is self-describing, so **lnav** will read the header to determine the shape of the file.