From cd90884dfcba46e1b3c622f662a9cf57b52266af Mon Sep 17 00:00:00 2001 From: esmerel <6818907+esmerel@users.noreply.github.com> Date: Wed, 11 Sep 2024 14:12:12 -0700 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Craig Norris <112565517+cnorris-cs@users.noreply.github.com> Signed-off-by: esmerel <6818907+esmerel@users.noreply.github.com> --- pipeline/parsers/decoders.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pipeline/parsers/decoders.md b/pipeline/parsers/decoders.md index fd0b11fc..4fb4016f 100644 --- a/pipeline/parsers/decoders.md +++ b/pipeline/parsers/decoders.md @@ -2,7 +2,7 @@ There are cases where the log messages being parsed contain encoded data. A typical use case can be found in containerized environments with Docker. Docker logs its -data in JSON format which uses escaped strings. +data in JSON format, which uses escaped strings. Consider the following message generated by the application: @@ -27,7 +27,7 @@ definition can optionally set one or more decoders. There are two types of decod - `Decode_Field`: If the content can be decoded in a structured message, append the structured message (keys and values) to the original log message. - `Decode_Field_As`: Any decoded content (unstructured or structured) will be - replaced in the same key/value, no extra keys are added. + replaced in the same key/value, and no extra keys are added. Our pre-defined Docker parser has the following definition: @@ -45,7 +45,7 @@ Our pre-defined Docker parser has the following definition: Each line in the parser with a key `Decode_Field` instructs the parser to apply a specific decoder on a given field. Optionally, it offers the option to take an -extra action if the decoder can't succeed. +extra action if the decoder doesn't succeed. ### Decoder options