Logchef CLI v0.2.3
Logchef CLI 0.2.3 fixes timezone handling.
Fixed
saved-queriesran the wrong window when a timezone was set. The window was formatted in UTC but sent with the configured zone, so withAsia/Kolkatathe server read the bounds 5h30m early. Saved queries now format and label the window in the same zone, likecollectionsalready did.findalso sends the resolved zone.- Invalid timezones are rejected.
logchef config set timezoneaccepts only IANA zone names such asAsia/KolkataorUTC. Abbreviations likeISTused to be saved and then silently replaced by the system zone at query time. config showanddoctorreport an invalid zone. A hand-edited config with an invalid zone now shows a warning with the zone actually in use, instead of printing the invalid value as if it applied.
Bundled skill
logchef skills get core now explains what the timezone setting affects: --from/--to and histogram bucket alignment. Row timestamps keep the backend's own offset, and times written inside sql queries are not converted. It also corrects tail (live stream by default, --poll for polling) and adds the LogchefQL 2.1 rules for quoting numbers and comparing with null.
Full Changelog: cli-v0.2.2...cli-v0.2.3