From: Anderson A. Giacomolli <agiacomolli@gmail.com>
Date: Tue, 10 Nov 2026 01:35:24 +0000 (-0300)
Subject: Explain daemon log levels and journal filtering
X-Git-Url: http://git.giacomolli.uk/onechat/commitdiff_plain/59e1537e1969f7c109084497287d729edbedba04

Explain daemon log levels and journal filtering

The README gives the short log form and the meaning of each level. The
journal example selects warnings and errors without the normal events,
so a user can find the failures that need attention.
---

diff --git a/README.rst b/README.rst
index 16aabce..18af256 100644
--- a/README.rst
+++ b/README.rst
@@ -219,6 +219,34 @@ login. To stop it, or also remove its start at login:
    systemctl --user stop onechat.service
    systemctl --user disable onechat.service
 
+************
+ Daemon log
+************
+
+The daemon writes short events with the part prefix and ordered
+``key=value`` attributes. An error cause comes last. Normal events use
+info, failures that can be retried or lose nothing use warning, and
+failures that lose data or stop work use error.
+
+With ``JOURNAL_STREAM`` set, each line carries a syslog priority without
+a time stamp or level word. The user journal can show only warnings and
+errors:
+
+.. code:: console
+
+   journalctl --user -u onechat -p warning
+
+The summary warning names its node. A schedule run has ``late`` only
+when it ran late:
+
+.. code:: text
+
+   <4>onechat: summary failed level=0 index=0: fake failure
+   <6>onechat: schedule ran id=1
+   <6>onechat: schedule ran id=2 late=1m0s
+
+Outside the journal, each line starts with the time stamp and level.
+
 **********
  Telegram
 **********