From 912877f25ad562ed4cafe7b2d7446bd48b477ea2 Mon Sep 17 00:00:00 2001 From: Kelly Brazil Date: Thu, 25 Mar 2021 15:34:54 -0700 Subject: [PATCH] additional timezone info --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 30f1e1a4..de06f543 100644 --- a/README.md +++ b/README.md @@ -70,7 +70,7 @@ Two representations of the data are possible. The default representation uses a > Note: Some parsers have calculated epoch timestamp fields added to the output. Unless a timestamp field name has a `_utc` suffix it is considered naive. (i.e. based on the local timezone of the system the `jc` parser was run on). > -> If a UTC timezone can be detected in the text of the command output, the timestamp will be timezone aware and have a `_utc` suffix on the key name. (e.g. `epoch_utc`) +> If a UTC timezone can be detected in the text of the command output, the timestamp will be timezone aware and have a `_utc` suffix on the key name. (e.g. `epoch_utc`) No other timezones are supported for aware timestamps. To access the raw, pre-processed JSON, use the `-r` cli option or the `raw=True` function parameter in `parse()`.