From 4d141d5ee5f708173aad90739907e3bea89669b0 Mon Sep 17 00:00:00 2001 From: Diogo Recharte Date: Thu, 10 Feb 2022 19:44:43 +0000 Subject: [PATCH] pipeline: parsers: json: fix typos Signed-off-by: Diogo Recharte --- pipeline/parsers/json.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pipeline/parsers/json.md b/pipeline/parsers/json.md index 686fe2898..25d7a5dce 100644 --- a/pipeline/parsers/json.md +++ b/pipeline/parsers/json.md @@ -1,6 +1,6 @@ # JSON -The JSON parser is the simplest option: if the original log source is a JSON map string, it will take it structure and convert it directly to the internal binary representation. +The JSON parser is the simplest option: if the original log source is a JSON map string, it will take its structure and convert it directly to the internal binary representation. A simple configuration that can be found in the default parsers configuration file, is the entry to parse Docker log files \(when the tail input plugin is used\): @@ -18,7 +18,7 @@ The following log entry is a valid content for the parser defined above: {"key1": 12345, "key2": "abc", "time": "2006-07-28T13:22:04Z"} ``` -After processing, it internal representation will be: +After processing, its internal representation will be: ```text [1154103724, {"key1"=>12345, "key2"=>"abc"}]