Hi Einar, thank you for the good question :) You can monitor both global and per-zone journal usage with kjournalprint utility (parameter -d) https://www.knot-dns.cz/docs/3.2/singlehtml/index.html#document-man_kjourna… The drawback is that the output form kjournalprint is intended for human reading, not really for script parsing. Anyway, with proper journal configuration, one should prevent any issues with journal becoming full. It's possible to set per-zone "soft" limits in a way that the effect of global "hard" limit never takes place. Hitting the "soft" limit only leads to some internal cleanup, not affecting DNS service in any way. Read more https://www.knot-dns.cz/docs/3.2/singlehtml/index.html#journal-behaviour Thanks, Libor Dne 05. 05. 23 v 11:01 Einar Bjarni Halldórsson napsal(a):

On 05/05/2023 11:01, Einar Bjarni Halldórsson wrote: Hello Einar, kjournalprint -dz will report journal usage, both per zone and total. The Knot DNS journal provides many advantages over plain files, but this is one of its major downsides, and needs careful monitoring. We have run into this at RIPE NCC as well. Older versions of Knot DNS didn't manage journal usage well, and it led to lots of fragmentation. I don't know which version of Knot you're running, but newer versions have improvements in the journal code to avoid some of those problems. If possible, you should upgrade to the latest version. Regards, Anand