Recognize omitted entries in a Core Lightning log snapshot
A gap between two events in getlog output can reflect level filtering or trimming of the in-memory logbook. Capture the omission markers during incident analysis.
Query an incident-level snapshot
Ask for unusual-or-higher records and print the logbook size along with skipped markers. On each SKIPPED record the count tells you how many entries are missing from this view.
lightning-cli getlog unusual | jq '{bytes_used, bytes_max, skipped: [.log[] | select(.type == "SKIPPED") | .num_skipped]}'
Avoid inferring a quiet interval
A skip count can include records below the selected level or records already dropped. Requesting a more detailed level can recover filtered entries still retained, but cannot resurrect trimmed entries. For a precise timeline, correlate the snapshot with persistent service logs and take their timestamp conventions into account.